Entering a Managed Organization
A request names the managed organization with theX-Managed-Account-Id header, as the Managed Accounts API describes.
managed_account.impersonate to send such a request. The request is then decided on the action of its route, messaging_profile.create here, for the same principal and the same roles in the manager org. The managed organization’s own roles never apply to it. A refusal answers 403 like any other denied request.
POST /v2/iam/roles/{role_id}/statements
A Delegation
Preview A delegation is created with each managed organization. It names the principals of the manager organization that may work there, with a role each, so a partner’s people get least privilege and every change in the managed organization’s audit log names the person who made it.GET /v2/iam/delegations/{id}
org:<org>/group:<group>, org:<org>/role:<role>, or org:<org> for everyone there. A new managed organization starts by granting its Owner role to whoever holds Owner in the manager org, and no other manager org user gets in until granted.
Defaults and Narrowing
PreviewPUT /v2/iam/delegation_defaults sets the grants every delegation starts with, and PUT /v2/iam/delegations/{id}/grants narrows one managed organization, down to read-only for the manager org owner if that customer asks for it.