Reference /Roles & capabilities
RECONCILIATION_ANALYST
Platform · roles and capabilities

Who can do what

Six roles, fifteen capabilities, taken verbatim from the platform’s own role table. A screen is not a permission — every guarded action checks its own capability at the moment it is attempted, and refuses in place rather than hiding.

Role VIEW_SUPPORTVIEW_FINANCEVIEW_CASESMANAGE_CASEHOLD_OPERATIONREQUEST_ADJUSTMENTAPPROVE_ADJUSTMENTEXECUTE_ADJUSTMENTFREEZE_WALLETUNFREEZE_WALLETSTOP_WITHDRAWALSQUARANTINE_PROVIDERBLOCK_ARCHIVE_OPERATIONARM_KILL_SWITCHFIRE_KILL_SWITCH Caps
SUPPORT_AGENT · · · · · · · · · · · · · 2
FINANCE_ANALYST · · · · · · · · · · · · 3
FINANCE_CONTROLLER · · · · · · · · · · 5
RECONCILIATION_ANALYST · · · · · · · · · · 5
ARCHIVE_OWNER · · · · · · · · · · · · · 2
INCIDENT_COMMANDER · · · · · · · · 7

No role holds both REQUEST_ADJUSTMENT and APPROVE_ADJUSTMENT. The two columns never light up on the same row. Separation is made impossible a step before dual control has to enforce it per request.

INCIDENT_COMMANDER can stop things but cannot move money. Breadth of blast radius is deliberately traded against the ability to adjust.

SUPPORT_AGENT sees one capability. Everything a support agent needs is a read — anything else routes to a request.