Rolling Out AI Company-Wide with Organizations, Roles and Lifecycle - Part 4

Organizations give each team its own space, roles give each person the right access in each one, and a clear lifecycle carries that access from a person's first day to their last, with a record of every change.

Rahul Singh, Founder, Multi-Router 7 min read

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

Create organization
NameOrganization IDCreatedActions
Engineeringadmin
org_Eng7Kp2QxV2026-02-09
ActiveRenameDelete
Supportadmin
org_Sup3Wm8RtL2026-03-17
OpenRenameDelete
Marketingadmin
org_Mkt5Hd9NcB2026-04-02
OpenRenameDelete
Salesadmin
org_Sls4Jv6YpG2026-05-21
OpenRenameDelete
Data Scienceadmin
org_Dsc8Tq3FzM2026-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.

us-west-2 · US West (Oregon)
The Organizations page for Example Co: an organization for each team, with Engineering selected.

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 leadAdminAdmin in every organizationManages everyone and everything.
Team leadMemberAdmin in EngineeringManages Engineering's people, policies and budgets.
EngineerNo Operator AccessMember in Engineering, with Portal accessWorks in Engineering in the dashboard, and sets up Claude Code from the Portal.
Support agentNo Operator AccessPortal access in SupportUses 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.

Engineering · org_3Fh8Wq2LdK

People

Invite person
People this page
6
Managed this page
5
Operators this page
3
Policies
1
Server page
1
AllPeoplePolicies
Filters
Search this page…
Name A–Z
Page 1 · 7 shown
2550
/ page
ExpandNameAccess PolicyLifecycle
Standard Engineering
policy:standard-engineering
Revision 3$200 Claude CodeLive
A
Alice Chen
alice@example.com
Operator· MemberPortal
Standard Engineeringactive
D
Dana Lee
dana@example.com
Portal
Standard Engineeringinvited
J
Jordan Kim
jordan@example.com
Portal
Standard Engineeringsuspended
M
Marco Ruiz
marco@example.com
Portal
Standard Engineeringactive
P
Priya Shah
priya@example.com
Operator· AdminPortal
Standard Engineeringactive
S
Sam Okafor
sam@example.com
Operator· Member
No policyactive
Search, filters, and sort apply to this server page.Policies are not paged with people; every policy shows on the first page.
Engineering's People page as its team lead sees it: each person's access, policy and state in Engineering.

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

Invite person
PeopleActivity
People
6
In this account
Admins
2
Can manage this roster
Portal users
1
Have agent portal access
Pending invites
1
0 expired
Search all people in this account
2550
Page 1 of 1 · 6 people

Search, filters and sort run across the whole account.

PersonStatus
AAisha Khanaisha@example.comActive

Identity

Email
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
Admin · role

Organization access

2 of 2
OrganizationDashboard rolePortal accessPolicy
EngineeringMemberOnEngineering agents
Admin · role · Portal · policy
SupportMemberOff—
Admin · role

Agents

Set up by the person in the portal.

OrganizationPolicyCreatedLast usedStatus
EngineeringEngineering agentsSep 2, 2026Sep 30, 2026ActiveRotate keyRetire

Activity

  1. Policy set to Engineering agents in Engineering
    by Priya Shah · Sep 2, 2026, 10:14 AM PDT
  2. Portal access granted in Engineering
    by Priya Shah · Sep 2, 2026, 10:14 AM PDT
  3. Added to Support
    by Priya Shah · Aug 21, 2026, 3:40 PM PDT
  4. Invite accepted
    Aug 14, 2026, 9:05 AM PDT
  5. Added to Engineering
    by Priya Shah · Aug 13, 2026, 4:22 PM PDT
  6. Account created
    by Priya Shah · Aug 13, 2026, 4:22 PM PDT
View all activity

Lifecycle

Resend portal linkSuspendOffboard
DDana Leedana@example.comActive
LLena Parklena@example.comSuspended
MMarco Ruizmarco@example.comActive
PPriya ShahYoupriya@example.comActive
TTom Beckertom@example.comInvited
The Account Roster with one person open: their identity, account and organization access, tools, activity and lifecycle actions.

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
InvitedInvited, with the invitation waiting for 7 days.
ActiveHolds access in the account or an organization.
SuspendedSigned out, with sign-in blocked and every tool stopped, and their access kept for when they return.
No accessOn the roster with every access removed, ready to be given access again.
Not set up and Pending approvalAdded 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.

M

Marco Ruiz

suspendedmember

marco@example.com

OperatorManaged agentsPortal

Account roster Reactivate Offboard
Access
Operator + agents
Organizations
1 of 2
Agents active
0 of 1
Spend this period
$41.75 / $200
Lifecycle
suspended
Sign-in
SSO linked

Access

Edit
Operator access
On · role member
OrganizationsEngineering· member
Managed agents
On·Portal
Engineering· Standard Engineering

AI agents

Claude CodedisabledEngineering · key …7Qx2 · issued Nov 2, 2026
Set up 12 days ago · router rt_9Hk3Ws7PzQ
$41.75 of $200 this month · $158 left
Rotate keySetup helpTrafficRetire

Policies

Engineering
Standard Engineering
Revision 3 · Claude Code
$200 per agent per month

Activity

Lifecycle events, newest page first.

active → suspendedNov 16, 2026
directory:inactive
Actor: directory
activeNov 2, 2026
Actor: usr_4Rb8Nq2KtV

Identity

Email
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

Claude CodeMonthly · resets Dec 1
$41.75 of $200$158 left
A person the directory suspended: their state, the Activity entry, and their tool stopped.

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

Invite person
PeopleActivity
Search activity
Date range

Search and filters run across the whole account.

AI agent set up in EngineeringforAlice Chen
by Alice Chen ·
Portal
Policy set to Standard Engineering in EngineeringforAlice Chen
by Priya Shah ·
Portal
Invite acceptedforDana Lee
Lifecycle
Portal access granted in EngineeringforDana Lee
by Priya Shah ·
Portal
Added to EngineeringforDana Lee
by Priya Shah ·
Membership
Account createdforDana Lee
by Priya Shah ·
Lifecycle
Policy set to Support Desktop in SupportforMarco Ruiz
Portal
Added to SupportforMarco Ruiz
Membership
Removed from EngineeringforMarco Ruiz
Membership
Account role changed to AdminforAisha Khan
by Priya Shah ·
Account role
AI agent key replaced in EngineeringforAlice Chen
by Alice Chen ·
Portal
Account suspendedforJordan Kim
Lifecycle
Account offboardedforTom Becker
by Priya Shah ·
Lifecycle
Portal access revoked in EngineeringforTom Becker
by Priya Shah ·
Portal
Page 1PreviousNext
The account's activity: invitations, organization and policy assignments, tools set up, keys replaced, suspensions and directory updates.

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.

Start for free

Create a router, set your SDK base URL to Multi-Router and see the cost of every request.