- The manager org owner is a superuser in every managed org, with the same full access as that org’s owner.
- Customer users manage their own resources in their managed org, limited to the actions their roles allow. They cannot change their own access, and they never see the manager org or other managed orgs.
- Manager org users enter managed orgs with only the actions their roles in the manager org allow.
- Each manager org team starts with a default role in every new managed org, and one managed org can be narrowed.Preview
- Guardrails apply in every managed org, and customer users cannot loosen them.Preview
- A manager org user who leaves loses access to every managed org at once.Preview
1. Create a Managed Org
In the manager org, the manager org owner creates a managed org for a customer with the Managed Accounts API.POST /v2/managed_accounts
password cannot be signed into directly unless a password is set later. An org’s owner is never limited by IAM, so a managed org with no owner sign-in keeps every customer user inside their roles.
Preview A delegation comes with the managed org, granting its Owner role to whoever holds Owner in the manager org. No other manager org user can see the managed org until granted.
2. Work in a Managed Org
In a managed org, the manager org owner acts with the managed org owner’s full access. A request names the managed org with theX-Managed-Account-Id header, and everything it creates or changes belongs to the managed org.
3. Give Customer Users Limited Roles
In the managed org, the manager org owner writes the roles and grants for customer users. Every/v2/iam request carries the header, so the role, the grant, and the setting all belong to the managed org.
id that GET /v2/organizations/users returns for the managed org. PATCH /v2/iam/settings with the header enables IAM in the managed org.
The customer user then sends messages and reads messaging profiles, and nothing else. Only an org’s owner manages IAM, so customer users cannot change any role or grant, their own included.
4. Let Manager Org Users In
In the manager org, the manager org owner gives manager org users a role that allowsmanaged_account.impersonate. Once the manager org has enabled IAM, a manager org user needs that action to enter any managed org.
POST /v2/iam/roles/{role_id}/statements