Skip to main content
IAM is turned on per organization. Until the owner enables it, roles and grants can be written and read but decide nothing, and every request is decided by the organization’s existing permissions, the ones set in Mission Control Portal and on service accounts.
Enabling IAM before the roles and grants exist locks out every user and service account without a grant. Every principal that must keep working needs a grant before the switch is turned.

The Switch

GET /v2/iam/settings returns the organization’s IAM settings. An organization starts disabled.
GET /v2/iam/settings
PATCH /v2/iam/settings enables IAM.
PATCH /v2/iam/settings
Only the organization owner reads or changes the setting. A change applies to new requests within five seconds.

What Changes

Enabling IAM is what makes roles decide. While it is off, grants exist but change nothing.
Working in a managed organization follows the same table. For users, the permission groups set in Mission Control Portal still apply as well, until they retire. A user then needs both a role that allows the action and, where the product checks a category, a group that allows it. Service accounts are decided by their roles alone.

Before Enabling

The order that leaves no gap is short.
  1. Write the roles.
  2. Grant one to each user and service account, and check the list with GET /v2/iam/grants.
  3. Enable IAM.

Disabling

{"enabled": false} returns every principal to its existing permissions within five seconds. Roles and grants stay as they are, so IAM can be enabled again without rewriting anything.