Skip to main content
Give a user or group tenant admin access, verify it, and revoke the grant when it is no longer needed. GitHub organization owners already hold tenant admin authority through the built-in murmur-org-admin-root tenant-binding. See Authorization for grant scoping and the permission reference for the capability inventory. Before you start, you need tenant-binding.create to add a grant, tenant-binding.delete to remove it, and tenant-binding.read to audit bindings. The group example also needs group.create and group.edit.

​
1. Create the binding

An unpatterned tenant-binding granting * gives its principals every permission on every resource. Bind a user directly or bind a group whose membership you manage separately.

​
A single user

Apply with murmur set:
The username is the GitHub login. No github_oauth/ prefix. Create the group first, then its tenant-binding, using murmur set:
Edit the group with murmur set to add or remove administrators without changing the tenant-binding.

​
2. Verify the grant

Confirm the new administrator can manage tenant resources. murmur check-permissions prints a PERMISSION, GRANTED, REASON table and exits non-zero if any permission is denied.
If a check returns no, confirm the tenant-binding names the user’s current login or a group they belong to.

​
3. Audit who has admin

Anyone with tenant-binding.create can promote others, including (in theory) promoting themselves to keep access if you remove them. Audit periodically with murmur get:
Read each tenant-binding with murmur get, including any referenced role. Look for unpatterned grants carrying *. The built-in murmur-org-admin-root tenant-binding names the dynamic murmur-org-admins group.

​
4. Revoke the grant

Remove authority supplied by your explicit tenant-binding. Other matching grants remain in effect. For a single-user binding, delete it with murmur rm:
For a group-based grant, you have two options. Delete the binding (revokes admin from everyone in the group at once):
Or keep the tenant-binding and remove the user from the group with murmur set:
To remove the built-in organization-owner authority, change the person’s GitHub organization role from owner to member, or remove their organization membership. Deleting a custom tenant-binding does not remove access supplied by murmur-org-admin-root.

Authorization

Full permission model, built-in roles, every kind and verb.

Service Profiles

Service Profiles for Flights and automated agents.