Org structure & teams

Your organization is structured so large operations stay tidy and access stays controlled:

Org  →  Business Unit  →  Team  →  Members

• Org — your company; the top of the tree.
• Business Unit — a division or region (e.g. "West Coast", "Catastrophe").
• Team — where the real work lives: owns profiles, assignments, and default capture settings (e.g. "Total Loss Fire", "California Theft Losses").
• Members — the people in a team, each with a role.

Create a business unit or team

1. Open Teams.
2. Select your org (use the organization switcher if you belong to several).
3. Add business unit, name it, save.
4. Inside the business unit, Add team, name it, save.

TIP

Model teams around loss types or workflows, not just geography. A team is where a profile's schema and capture settings live, so "Theft — CA" and "Total Loss Fire" as separate teams keeps each one's rules clean.

Team defaults

Each team has default capture settings — timestamp, GPS, and watermark preferences that new assignments inherit. Set these once per team so every assignment starts consistent; you can still override per assignment.

Members & roles

Manage who's on a team and what they can do under Members (and per-assignment under Access). Roles range from team admin down to observer — see Roles & permissions for the full matrix.

IMPORTANT

Roles are scoped. A team admin manages their team; an org admin manages everything. Assignment-level invites (collaborator/observer) only grant access to that one assignment — claims stay isolated from each other.

Next: Profiles & the schema builder.