01must proveConfirmed | Assignment creation, withdrawal and scope changes require access-management permission covering the target scope; read-only authority cannot write grants. | permission | api, service | test |
02must proveConfirmed | Delegation requires the administrator to hold every affected permission unconditionally and without a deny at the target scopes; failures identify the missing keys and scopes without disclosing others’ grants, and self-widening fails. | permission | service | test |
03must proveConfirmed | Customer assignments can cover the whole customer, one of its workspaces or an existing unarchived custom record type in a workspace; unsupported single-record kinds fail. | validation | api, service | test |
04must proveConfirmed | Customer security operations cannot create or amend platform-scope staff authority, including its duration, conditions or scope, and refusals direct staff to HQ. | permission | service | test |
05must proveConfirmed | Assignments for active memberships are active, assignments for invited memberships remain pending until acceptance, and future validity windows contribute no access until they open. | lifecycle | service | test |
06must proveConfirmed | A person can hold only one non-revoked role assignment for the same scope and validity window; sequential or concurrent duplicates fail, and revocation allows a replacement grant. | invariant | service, database | test |
07must proveConfirmed | Withdrawal preserves assignment history, guards against losing the last administrator and requests an authorizer flush after commit without guaranteeing eviction of cached decisions. | lifecycle | service | test |
08must proveConfirmed | Setting role scope atomically reconciles customer-wide or 1–100 selected-workspace assignments, retains matching rows, creates missing rows under delegation checks and revokes unwanted rows; outside-customer workspaces fail and resource assignments remain unchanged. | calculation | service | test |
09must proveConfirmed | Weakening an assignment’s deny by narrowing scope, shortening validity or adding a condition requires widening authority; extending validity or removing that restriction can strengthen the deny instead. | permission | service | test |
10Confirmed | Grant checking reports the role and whether the caller can assign it at a proposed scope without making a write, including checks within a workspace administrator’s scope. | policy | api, service | test |
11must proveConfirmed | Access explanation evaluates a member’s permissions and traces allowed keys to assignments, roles and policies; denies remove keys and absent grants produce an empty explanation. | calculation | service | test |
12must proveConfirmed | Staff-only roles and roles outside the customer cannot be assigned to customer memberships and are presented as not found. | permission | service | test |
13must proveConfirmed | Assignment creation, withdrawal and scope changes produce both assignment and membership history entries. | invariant | service | test |
14Confirmed | Role-member pagination includes only reached people holding the role and presents each assignment’s scope. | policy | api, service | test |