Team

Invite colleagues, assign responsibility, and remove access without leaving the organization or its automation without an owner.

Membership makes someone part of the organization. Roles and resource grants determine what they can do. Keep both together when a colleague joins, changes responsibility, or leaves.

Invite the right identity with the intended authority #

Invite the colleague's email address and choose the authority they should receive. Invitation management needs org:manage_team or the corresponding invitation policy. Check for an existing pending invitation before creating another for the same person.

The invited person accepts while signed in with that email address. A service key cannot accept an invitation. If the account does not match, correct the identity or invitation instead of passing the token to another account. For an expired or revoked invitation, inspect its current state before retrying.

With RBAC enabled, invitations cannot grant Owner authority. Invite the person first, then use the protected ownership operation after they join. The caller cannot delegate permissions beyond their own. Update a pending invitation when the intended role changes before acceptance.

Without RBAC entitlement, invitation role resolution falls back to Owner. Confirm that broad authority before sending; an absent custom-role selector does not mean restricted access. RBAC entitlement transitions can also reset existing members and pending invitations to Owner, as described under Access changes.

Match roles to responsibility #

Members can inspect the member list. Role assignment needs RBAC and org:manage_team, with checks preventing permission escalation. A member with no assigned role can still hold additive resource grants. Clearing a role therefore differs from ending membership.

Only an Owner can promote another Owner or remove Owner authority, and at least one Owner must remain. Before stepping down or leaving, promote the successor and verify the assignment. The last-Owner guard protects continuity; the organization still needs to choose the appropriate successor.

Remove access and check dependent callers #

Use removal or leaving to end one person's participation. Inspect the automation they maintained. Personal API keys follow their creator's current membership and lose access to the organization when that membership ends. Organization service keys remain independent and need their own scope or revocation review.

Check pending invitations, shared-resource grants, and ownership continuity alongside credentials. Do not delete the organization to solve a member departure. API keys explains credential replacement and revocation.

After the change, inspect current membership and role state and any available audit record. Have the affected caller verify its intended access through the supported interface rather than sharing a broader key to bypass a refusal.