Access, roles & approvals

Users and role permissions

The API uses token-based authentication. Role-menu records control menu access and action-authority lists. A global server-side action filter enforces mapped write operations. The built-in administrator is a full-access role; role-menu and approval configuration are administrator-only.

The recorded picker-role fixture could read authenticated data but received HTTP 403 for an unauthorized user-creation request. This is scoped evidence, not certification of every permission and tenant boundary.

Approval definitions are not approval execution

Flow definitions, nested maps, assigned approvers and conditions can be configured through tenant-scoped endpoints. Those configuration paths have recorded QA. Transaction-specific approval execution endpoints and decision screens are unavailable in this implementation. Do not design a mandatory approval process around them yet.

Before exposing an installation

• Replace demo credentials, configure token secrets, enable HTTPS and restrict administrative access.
• Test roles and tenant isolation against real business responsibilities. Review unmapped workflow-action aliases.
• Set retention, backup, recovery and incident responsibilities. Server location alone does not establish data-protection compliance.