Guides

Dashboard and Queues

Understand the operational dashboard, queue types, and how work is surfaced to different roles.

DashboardQueuesOperations
Last updated March 8, 2026

Dashboard purpose

The dashboard gives users a live operational view of the work that matters most. Common cards and queues include My Approvals, In Review, Blocked, Overdue, and Recently Updated.

My Approvals

This queue shows changes requiring action from the current reviewer. Use it to prioritize direct responsibilities first.

In Review

This queue shows changes actively moving through the governance process. It helps teams monitor throughput and active operational exposure.

Blocked

Blocked changes are typically waiting on missing evidence, unresolved safeguards, or other required conditions.

Overdue

Overdue approvals show where review timing has slipped past expected SLA. This is often one of the most useful operational signals for admins and executives.

Recently Updated

This view helps users stay aware of current activity without opening every individual change.

Visibility behavior

Dashboard cards and queues reflect org role permissions, domain permissions, restricted visibility, and assigned-reviewer logic where applicable.

Submitter: Focus on drafts, in-review owned changes, and blocked items you need to unblock.

Reviewer: Focus on My Approvals, blocked-by-evidence changes you are reviewing, and overdue items.

Admin / Owner: Focus on org-wide operational health, overdue work, blocked work, and review bottlenecks.

Executive: Focus on high-risk changes, blocked and overdue items, and broader risk visibility.

✏️ Edit this page on GitHub
Was this page helpful?
Send feedback