Goal: define a role once, hand it to several people, and change what all of them can do by editing one row.
Concepts: org-management capabilities, :role, role membership,
the Roles panel, why a role is not a namespace grant.
Prefer to be shown? This lesson exists as a guided in-editor tour — pick “Interactive tutorial” in the account menu. It needs an organization and the
manage-rolescapability; without them the catalogue lists it, disabled, with the reason on the row.
Lesson 28 drew the line and this lesson picks up the other side of it. There are two independent axes of permission:
| Namespace grants (Lesson 28) | Org-management capabilities | |
|---|---|---|
| Answer | may this person touch acme.billing? |
may this person administer the org? |
| Values | read, write, execute, admin, bind-args, append-list, view-impl |
manage-users, manage-grants, manage-roles, manage-apps, publish-packages |
| Scope | one namespace subtree | the whole org |
| Bundled by | — | a role |
admin on a namespace does NOT imply manage-users. Ownership of the
org implies all of the management capabilities, implicitly — that is
what makes the owner the owner.
A role is a named bundle on the second axis: {name, capabilities,
members}. Nothing more. It exists so you can say “these three people
run the org’s membership” once, instead of issuing the same capability
to three people and remembering all three when it changes.
Account menu → Organization → Roles (gated on manage-roles,
so an org owner always sees it). One row per role:
support manage-users, manage-grants alice, bob ×
Because the alternative rots. Issue manage-users to three people
individually and the org’s answer to “who can invite members?” is
spread across three rows that nothing ties together. Six months later,
tightening the policy means finding all three.
With a role, the answer is one row, and changing it changes everyone’s
effective capabilities at once — the next request each of them makes
already reflects it. This is the same argument lesson 03 makes about
parent-ids and lesson 32 makes about packages: name the shared thing
once, and let the places that need it point at the name.
support role
with manage-users lets alice invite people; it does not let her
read acme.billing. That is a grant (Lesson 28), and it stays
separate on purpose — administering an org and reading its code are
different powers, and plenty of people should have exactly one of
them. A role can, however, be the subject of such a grant: type
the role’s name in the grants form and every member holds that
namespace grant — the team is the unit, membership is edited here.acme means nothing in globex,
even for the same account (lesson 33).A member’s effective org capabilities are the union of:
The editor reads that union out of the capabilities header on every
response, which is why a panel the reader may not use is simply not
rendered — the Members panel is absent without manage-users, the
Roles panel without manage-roles. Nothing is hidden that would
otherwise work; the affordance and the permission are the same fact.
(An org owner — or a manage-roles holder — on an instance with the
tenancy addon.)
support, tick manage-users, + Add role. The row
appears with an empty member list.