Roles and permissions

The eleven Role flags, the credential activity layer, and second-person approvals.

Access is checked in two layers: the Role flags and the person's StaffCredential.

Role flags

FlagAllows
canAccessDashboardEnter the dashboard and read Role records
canManageOnboardingRun runCannabisOnboarding
canManageAuthorityRenew authority, edit premises details
canManagePeopleStaff and customer identities, credential revoke
canManageRolesManage roles
canManageComplianceEligibility, rules, holds, recalls, incidents
canManageInventoryReceive packages, lab results, release for sale
canManageSalesCarts, POS, fulfillment
canManageFinanceTenders, refunds, shifts, cash
canManageIntegrationsProvider queues and payment providers
canViewReportsAudit log and reconciliation

Roles cannot be created, updated or deleted through generic GraphQL.

Credential activities

A credential lists allowedActivities. Each command names the activity it needs: inventory, sale, cash, eligibility, state_reporting, incident or authority. A missing activity returns Current staff credential does not authorize this activity.

Second-person approvals

Some commands need an independent approver who re-enters their own password for that one command:

CommandApprover needs
releasePackageHoldcanManageCompliance (error: Hold release requires an independent compliance approver)
advanceRecallCase when closingCompliance
closeRegisterShiftFinance
approveCashVarianceIndependent finance actor (An independent finance actor must approve this variance-review shift)
refundCannabisSaleFinance

The approver cannot be the person acting.

On this page