The job of this console
See what is late, open the inbox, decide on the source request. Change routing on Admin policies, not here.
Analytics · Approvals
Approvals Analytics
SLA and volume on the universal approval engine — charts on live requests, not a second inbox.
Scroll to Flowcharts. Scenario: Read approvals analytics then open the inbox.
SLA grain
Aging you clear in the inbox
Approvals analytics shows volume and SLA on the same engine My approvals uses. Charts do not approve anything.
Analytics → Approvals analytics
Route
/analytics/approvals
Org flag approvalsEnabled
Manager · HR Admin · Admin
Seat at the table
Managers, HR admins, admins with approvalsEnabled.
The working rhythm
Scan aging, jump to My approvals, decide, refresh.
Moments that bring you here
A backlog spike. SLA report. After a policy change. When a delegate seems missing.
ⓘ
Engine is shared
Leave, timesheet, and attendance stay on their records. This pack only visualizes the engine.
Flowcharts
1 — Aging then the inbox
See SLA heat, decide on My approvals or the source request.
flowchart TD
A[Open Approvals analytics] --> B[Read SLA / volume]
B --> C[My approvals]
C --> D[Decide on source request]
D --> E[Pack refreshes]
- 1OpenAnalytics → Approvals analytics.
- 2ScanAging by domain.
- 3InboxMy approvals.
- 4DecideOn the leave, timesheet, or other request.
Overview
Approvals analytics composes the universal approval engine. It does not replace My approvals or Admin policies. Leave, timesheet, and attendance requests remain the source records.
How to use
1. Protected flows
Do not invent a parallel approve path from this pack.
2. Delegation overlay
Acting managers still configured on Delegation.
3. Mask
Medical leave reasons stay off exports.