Statuses and permissions
Oroko uses status and role information to control editing, review and administration.
Process statuses
Section titled “Process statuses”The current formal process statuses are:
- Draft — working process content.
- Under Review — submitted for a formal decision.
- Approved — approved and locked.
- Changes Requested — returned for further work.
- Archived — retained outside the active process set.
Workspace roles
Section titled “Workspace roles”Workspace access currently uses:
- Owner
- Admin
- Editor
- Standard
- Viewer
Owners and Admins can manage workspace membership.
Editors, Owners and Admins can submit work for review through workspace permissions.
Process-specific roles
Section titled “Process-specific roles”A process can further apply process-specific access.
Governance recognises process roles including:
- Editor
- Standard
- Reviewer
- Viewer
A process Reviewer can make review decisions. Process-specific access can restrict collaboration beyond the workspace-level role.
One permission model
Section titled “One permission model”Oroko applies the same core permission model across the browser application, REST API and Public MCP.
Developer keys and MCP access do not bypass normal workspace or process permissions.