Roles and permissions
This is the designed rule set for every persona in Risk Core. Every act is limited to the entity where the role is granted.
R = read · A = act (create, edit, sign off) · — = no access.
A role at a parent entity reads downward and never acts on a subsidiary’s records (Subsidiary-Independence).
ERM Core
Section titled “ERM Core”| Persona (role) | RCSA | Loss Event | KRI | BIA | Dashboards | Admin |
|---|---|---|---|---|---|---|
| Risk Champion | A — drafts own team’s risks and filing | A — reports | R; enters observations if owner | A — drafts activities for own team | own scope | — |
| Reviewer | A — review / return | R | R | R | own scope | — |
| Approver | A — approve | R; sensitive events at once | R | R | own scope | — |
| Entity Risk Manager | A — reopen, period work | A — validate / reject | A — define, calibrate | A — approve | entity + beneath | people, roles and org for own entity |
| Executive / RMC | R | R (sensitive: once in the reporting line) | R | R | entity + beneath | — |
| Group RM / Group Reader | R whole tree; group RM acts only at the root (open year, group configuration) | R (validated only) | R | R | group roll-up | — |
| Administrator (platform) | R | R (non-sensitive) | R | R | all | people, roles, org, every entity; never acts on client records |
BCP Core
Section titled “BCP Core”| Persona | Own check-in | Sees status of | BCP level | Call tree | Staff list and accounts | Delete check-ins |
|---|---|---|---|---|---|---|
| Staff | A | own team, no sensitive detail | R | report in | — | — |
| Team head | A | own team at the HR level | R | report in; alternate for their team | — | — |
| Line executive | A | whole line, no sensitive detail | R | report in | — | — |
| HR (org admin) | A | whole entity | R | report in | A | A (MFA) |
| BCP head | A | whole entity | orders the level | activates | — | — |
| Operator (delegated, named) | A | whole entity | enters the level once activated | operates | — (by design: an operator cannot edit the staff list) | A only while activated, with MFA |
| Platform admin (Qirin X) | — | — | — | — | — | — ; switches the public CSR path |
How the matrix is enforced
Section titled “How the matrix is enforced”- Buttons appear only when the role allows the action on the entity you are viewing.
- The database refuses the action regardless of the screen — see Security and data.
- One person can hold several roles; each role keeps its own scope. See Your roles and where to start.