Client role map — internal key mapping
The client-facing role map, .forge/client/roles-and-permissions.md, is written in Empire’s terms
and goes to the client. This page holds the internal side of it: which decisions it restates, and
how its terms map to the permission keys in the code. It moved here on 2026-09-27 so that the client
document carries no internal references.
What the client document restates
-
Optional advice on role contents, the Tea Room and Executive roles included. OQ-53 is closed as not required, because every role is Empire’s configuration.
-
The decided answers to OQ-51 (provisioning and offboarding), OQ-52 and OQ-54 (
info@by forwarding), OQ-56 (the four reporting-hierarchy policy questions, its Section 2) and the Q3 Managing Director arrangement. -
The model:
- AD #34: configurable roles on the minimal view/manage catalog; the Flyway-seeded IT Admin; unlimited self-escalation and no coded separation of duties; the last-admin rule.
- AD #35: one owner,
record_share, own/team/all reach, transitive sharing, the eligible-only picker. - AD #36: the audit trail.
- AD #37: no scope on a grant — every key reaches down the reporting line, and the “All
records” tick is the entity’s
allkey (the client document’s Rule 2, revised 2026-09-27).
These refine AD #30, AD #32 and PRD Rev 29; AD #26 stands.
Client terms to permission keys
| Client term | Key |
|---|---|
| View / Manage on an area | <entity>.view / <entity>.manage |
| Hand over, share, remove a share (A-34, A-37, A-38) | the entity’s manage, with the record in reach by any path — ownership, the reporting line, the all key or a share (AD #35 D-1; lead confirmation 2026-09-30, PRD Rev 46) |
| All records on an area | <entity>.all — lead.all, account.all; deal.all, quote.all, sample.all in Phase 2 (AD #37; added to the catalog by F5-l) |
| The standards book | buying_standard.* |
| System settings, user and role administration included (the role editor’s “Manage settings, users and roles”) | settings.manage — one key since AD #34’s refinement of 2026-10-26 (signed off by Tharinda, 2026-10-27), which folded the separate access.manage into it |
| Your own mailbox | email.manage |
| Publish the weekly prices | price.publish |
| Approve a below-floor quote | quote.approve_sub_floor |
| Use the capture app (the client document’s 4.7 and A-41) | capture.use — its own key since PRD Rev 95 (FS-6 Rev 23), where it was proposed under lead.manage |
One mapping is a proposal, not a catalog decision: shared sequence templates under
settings.manage (the client document’s 4.4).
Saved views (its 4.5) need no key: creating, sharing and reading views follow the list’s view key (FS-6 Appendix A, decided by F32-d FR-V5; PRD Rev 87). The rendering rule is
design-system §9. The catalog itself is FS-6 Appendix A as F5-k revises it.
On sign-off
Fold Empire’s answers back per .claude/rules/prd.md, and into the recommended day-one roles that
Empire’s Administrator creates (AD #32, AD #34).