Help Center/Governance, RBAC & Security Desk/How to read permission risk, scope and approval flags
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to read permission risk, scope and approval flags

Explains the columns of the Permission Catalog: key, granularity, risk, default and supported scopes, and the approval lock.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Permission Key

The key in module.resource.action form, its human name underneath, and an amber shield icon (tooltip "System protected") for protected permissions.

2

Granularity

A grey chip with how fine-grained the permission is.

3

Risk

A chip coloured LOW (green), MEDIUM (blue), HIGH (amber) or CRITICAL (red).

4

Default Scope and Supported Scopes

The scope applied by default and the list of scopes the permission can be granted at.

5

Approval

A padlock means the permission requires approval; a dash means it does not.

Expected Operational Outcome

You can judge how dangerous a permission is and at which scopes it can be granted before adding it to a role.

Was this guide helpful?

Help us refine our platform documentation