In Part 3 I talked about directory sync, which sends people and groups from the company's identity provider and turns each group into an organization, a role and a tools policy. In this post I want to cover what those organizations and roles are: how a company gives each team its own space in Multi-Router, how each person gets the right access in each one, and how access follows a person from their first day to their last.
Organizations for Every Team
A Multi-Router account holds the company's people, and organizations divide the work between teams, such as Engineering, Support, Marketing and Sales. Each organization has its own provider keys, tools policies, budgets, API keys, prompts and Traffic, so every team works, spends and is measured in its own space. The Engineering team's Claude Code policy, its Anthropic account and its $20,000 monthly budget belong to Engineering, and the Support team never sees them.
Single sign-on and directory sync are set once for the account and cover every organization, so people sign in the same way wherever they work. An account holds up to 25 organizations, and the account itself works as one more, for resources the whole company shares. Each person switches between the organizations they belong to from the profile menu.
Organizations
Manage organizations you belong to. Open one from the profile menu or the table below.
Your organizations
5 organizations
| Name | Organization ID | Created | Actions |
|---|---|---|---|
Engineeringadmin | org_Eng7Kp2QxV | 2026-02-09 | ActiveRenameDelete |
Supportadmin | org_Sup3Wm8RtL | 2026-03-17 | OpenRenameDelete |
Marketingadmin | org_Mkt5Hd9NcB | 2026-04-02 | OpenRenameDelete |
Salesadmin | org_Sls4Jv6YpG | 2026-05-21 | OpenRenameDelete |
Data Scienceadmin | org_Dsc8Tq3FzM | 2026-08-11 | OpenRenameDelete |
Default region
Fallback region for region-bearing providers (Bedrock) when neither the router nor the provider key pins one. Applies to the Example Co. account.
Roles and Access
Every access question in Multi-Router comes down to one rule: is the person an admin of the organization they have selected? An admin of Engineering manages Engineering's people, policies and budgets, and nothing else. An account admin is an admin of the account itself, and sees every person and every organization in it.
Each person has an account role, and in each organization a dashboard role, Portal access, or both. Portal access is separate from the dashboard role, so a person can set up their own tools without any access to the dashboard.
| Person | Account role | Organization access | Result |
|---|---|---|---|
| Platform lead | Admin | Admin in every organization | Manages everyone and everything. |
| Team lead | Member | Admin in Engineering | Manages Engineering's people, policies and budgets. |
| Engineer | No Operator Access | Member in Engineering, with Portal access | Works in Engineering in the dashboard, and sets up Claude Code from the Portal. |
| Support agent | No Operator Access | Portal access in Support | Uses Claude Desktop set up from the Portal, and only ever sees the Portal. |
This lets a company hand each team to its own lead. The Engineering lead invites engineers, assigns their policies, approves requests for more budget and watches the team's spend, without holding admin access to the whole account.
People
Inviting and Managing People
One invitation gives a person everything they need: their account role and, for each organization, their dashboard role, Portal access and tools policy. Account admins invite from the Account Roster, and team leads invite into their own organization from its People page. The person accepts by signing in with the invited email, through single sign-on when the account requires it, and starts in the organization the invitation grants. With directory sync, the identity provider adds people on its own.
The Account Roster lists everyone in the company in one place, with their state, role and access in every organization. It filters by status, by source (the directory or an admin), by access and by organization. Opening a person shows their identity, their access in each organization, the tools they have set up, their activity, and the actions to suspend, restore or offboard them.
People
Everyone in this account
Search, filters and sort run across the whole account.
Identity
- aisha@example.com
- Person ID
- per_9Kd4Xv2QmT
- Added
- Aug 13, 2026
- Last sign-in
- Sep 29, 2026
Account access
- Account role
- Member
- Portal access
- Off
Organization access
Agents
Set up by the person in the portal.
Activity
- Policy set to Engineering agents in Engineeringby Priya Shah · Sep 2, 2026, 10:14 AM PDT
- Portal access granted in Engineeringby Priya Shah · Sep 2, 2026, 10:14 AM PDT
- Added to Supportby Priya Shah · Aug 21, 2026, 3:40 PM PDT
- Invite acceptedAug 14, 2026, 9:05 AM PDT
- Added to Engineeringby Priya Shah · Aug 13, 2026, 4:22 PM PDT
- Account createdby Priya Shah · Aug 13, 2026, 4:22 PM PDT
Lifecycle
The Lifecycle of a Person
Every person moves through a clear set of states, from invitation to offboarding, changed by an admin or by the directory:
| State | Meaning |
|---|---|
| Invited | Invited, with the invitation waiting for 7 days. |
| Active | Holds access in the account or an organization. |
| Suspended | Signed out, with sign-in blocked and every tool stopped, and their access kept for when they return. |
| No access | On the roster with every access removed, ready to be given access again. |
| Not set up and Pending approval | Added by the directory and waiting for access or for an admin's approval. |
Suspending a person takes effect at once. They are signed out of the dashboard and the Portal, their tools stop working, and their organizations, policies and settings stay as they were, ready for the day they return, such as after a leave. Removing a person's access retires the tools they set up and deletes their keys, and asks for confirmation first when those tools were used recently. Offboarding removes the person from the account for good, and their name and history stay in the activity log.
The account always keeps an owner who can manage it, and nobody can suspend or offboard themselves, so a mistake or a departure never locks a company out of its own account.
Marco Ruiz
suspendedmembermarco@example.com
OperatorManaged agentsPortal
Access
EditAI agents
Policies
Activity
Lifecycle events, newest page first.
Identity
- marco@example.com
- Account role
- member
- Sign-in
- SSO linked
- Person ID
- per_6Jd3Xv9PmL
- User ID
- usr_4Rb8Nq2KtV
- Created
- Nov 2, 2026
- Updated
- Nov 16, 2026
Budget
A Full Audit Trail
Every change to people and their access is recorded with who made it and when: invitations, role changes, policy assignments, tools set up and retired, keys replaced, suspensions and every update from the directory. Each policy also keeps its own history of revisions, with who saved each one. The trail stays after a person leaves, so the company can always answer who had access to which tools and when.
People
Everyone in this account
Search and filters run across the whole account.
The Complete Rollout
Over four parts, this series has covered a company-wide AI rollout from end to end. Part 1 gave each person their own tools, models and budget from a tools policy and the Portal. Part 2 signed them in through the company's identity provider. Part 3 synced them from the directory, so access follows each person as they join, move and leave. Part 4 organized them into teams, roles and a lifecycle, with a full record of every change. Attributing AI Cost to People and Tools covers how the spend from all of it is tracked and budgeted, and the Organizations & People docs cover every role and setting in detail.