Background

A ready-made dashboard view for administrators that composes the approvals gadgets into one default layout focused on the question: is the approval process healthy across everything I administer. Unlike the personal view, it is instance-wide rather than scoped to the viewer, and it answers a monitoring question rather than an action queue. One layout serves both audiences through the visibility model: the global admin sees every approval in the instance, and the space admin sees the same sections with all data narrowed to the spaces they administer. The view is built from predefined templates so the administrator does not configure each gadget from scratch. The attached HTML mockup shows the target layout.

Default admin layout

Section order runs from current operational state at the top to analytical breakdowns below:

• Instance KPI strip: one row of four figures for the active scope (open approvals, resolved, median cycle time, expired rate).

• At-risk approvals: an urgency card with three counters (Overdue, Expiring, Stalled) and a list of the most pressing items, showing who each is waiting on. Anchored to today. Separate ticket.

• Cycle time by definition and Volume by definition, side by side. Volume bars are coloured by rejection-rate band (Healthy under 5 percent, Balanced 5 to 15 percent, Concerning 15 to 25 percent, Broken over 25 percent).

• Load by approver and Approver responsiveness, side by side. Groups appear in Load but are excluded from responsiveness.

• Instance summary: Created vs Resolved next to Approval outcomes by definition.

Filters and behaviour

Space, Definition and Range narrow every section, with a 30-day default range. A separate User filter applies only to Load, Responsiveness and At-risk, highlighting the person within the ranking; it does not affect the definition and throughput cards. At-risk is anchored to today and ignores the range. List cards expose extra rows through a Show more control. A dark mode is available. Each section has a tooltip.

Acceptance criteria

• One layout serves both audiences: the global admin sees the whole instance and the space admin sees the same sections with data narrowed to the spaces they administer; the active scope is shown in the header where a single space applies.

• Sections render in order: KPI strip, At-risk, cycle time and volume by definition, load and responsiveness by approver, Created vs Resolved plus outcomes.

• The User filter applies only to Load, Responsiveness and At-risk and does not affect the definition and throughput cards.

• Volume by definition colours bars by rejection-rate band with the stated thresholds; Approver responsiveness excludes groups.

• The view is composed of predefined templates; the attached HTML mockup is the layout reference.

Notes

The At-risk approvals card and the preset catalogue are separate, related tickets. This ticket covers composing the default admin layout and its global and space-admin scoping, not the individual gadget types. The HTML mockup will be attached.