Decisions and approvals
Two admin screens about the people in the loop: Decisions shows whether they are keeping up with what agents ask, and Approvals is the queue of report versions a publishing rule has held.
Both screens are for owners and admins. Neither is where a person decides their own requests; that is their inbox. These show the organisation as a whole.
Decisions
Admin → Decisions covers the approval requests made in your organisation over the last 7, 30 or 90 days; choose the window at the top right. Every number is for the whole organisation.
| Tile | What it counts |
|---|---|
| Asked | Approval requests made in the window, with the share that came from agents. |
| Approved | The share of decided requests that were approved, with how many were decided. |
| Median time to decide | Half of decided requests were answered within this time; the note gives the time within which 90% were. |
| Expired unanswered | The share that ran out with nobody answering. |
| Open now | Requests still waiting, however long ago they were asked. |
| Settled by policy | The share of gated actions a gate rule allowed without asking anyone. |
Below the tiles, Requests per day stacks each day's requests by how they ended: approved, rejected, expired, or still pending or withdrawn. Hover a day for its numbers. In a very busy window only the most recent 10,000 requests are counted, and the chart says so.
Waiting on, and oldest open requests
Waiting on lists who has open requests right now, most first, with the date of their oldest. Oldest open requests lists the requests that have waited longest, with who asked, when, when they expire and their risk; open one to see it in full.
If someone on the list is away, they can set cover in their own settings: while it runs, requests that name them also reach the colleague they chose, and anything already waiting on them is passed on too. They stay on every request. See Your settings.
Ethics concerns
This panel shows whether your ethics rules are doing useful work:
- How many requests in the window put a concern to the approver, and what share of all requests that is.
- Of the flagged requests that were decided, the share approved anyway, each with a reason.
- How many concerns were raised under each principle.
The Settled by policy tile links to the gate, which shows the rules behind it and every decision. See Policies.
Approvals
Admin → Approvals is the queue of report versions that a publishing rule with the effect Needs approval has held. A held version is stored and scanned, but nobody is served it. The rules that hold publishes are switched on in Admin → Policies; see Publishing policies.
Each row shows the report, the version, whether it is a new report or which version readers see today, who published it (a person or an agent), when, their summary of the change, and which rule held it and why.
- 1
Read it
Preview opens the held version as you, in a new tab. Compare with live puts it beside what readers see today, when there is a live version.
- 2
Approve
The version goes live, with every notice an ordinary publish sends.
- 3
Or decline
Optionally tell the publisher why, then confirm. The version stays in the report's history, and readers never see it. The publisher is told.
Approval requests that are not publishes, such as an agent asking before it acts, are not in this queue. They go to the people named on them, in their inbox, by email, and in Slack or Teams if connected. See Deciding an approval.
Evidence
Every request, decision, reason and change is recorded in the audit log, with who did it and when. To hand someone the record of one piece of work, export an evidence pack from its flow or report: every step, who was asked and what they said, as JSON, CSV or PDF. See Flows and evidence packs and Security, audit and legal holds. Deliverd describes this as tamper-evident history, not cryptographic immutability.