Appearance
Work & Decisions
The connective layer that makes governance work: how OrviQ decides who must act, tells them, tracks whether they did, and records the decision.
Pages in this area
| Page | Route | What it does |
|---|---|---|
| Workbench | /my-work | Your personal queue of governed work |
| Approvals Hub | /approvals | Every governed decision awaiting action |
| Alerts Center | /alerts | Active alerts and their sources |
| GRC Calendar | /calendar | Governance obligations with dates |
| Reports | /reports | Operational reports and exports |
| Employee Policy Portal | /my-policies | Self-service employee policy reading and version-pinned attestation |
Documentation for this area
| Article | What it covers |
|---|---|
| Enterprise Workflow overview | The separation of concerns |
| Workbench | The nine buckets and the single-claim rule |
| Approvals Hub | Working an approval queue |
| Employee Policy Portal | Version-pinned policy attestations, reading verification, and reasoned declines |
| Notifications | Event, notification and task |
| GRC Calendar | What belongs on it and what deliberately does not |
| Multi-Eye Approvals | Four, six and eight-eye chains |
| Segregation of Duties | Enforcement and the governed break-glass |
| Decision History | The audit trail behind every decision |
Three things that are not the same
An event means something happened. A notification means someone may need to know. A Workbench task means OrviQ is waiting for a specific person to act.
Automated events never create tasks. A Workbench full of machine activity is a Workbench nobody reads.
Permissions and entitlement
The organisational workflow layer is core infrastructure and is not separately entitled. Key permissions: work.read, work.assign, ownership.accept, workflow.approve, workflow.configure. Access to /my-policies is granted to all authenticated workspace roles via policy.attest.