6 lines in your history in the last 11 days (2 September – 12 September) — every change to money, licenses and access, and every AI request, kept in the trail.
Times in UTC.
6 events in the records read occurred in the last 7 days. This is a count of events, not of things you have not read. Aristo keeps no per-person read state. Counts cover only records read, not the complete organization. Open approvals remain visible beyond the activity window.
Open approvals and the last 30 days
Open work first, then recent activity. Every row opens the surface that holds the thing it is about.
- Monthly department chargeback — April 2026 – September 2026 is ready Generated on demand and filed in the library. Its figures are frozen as they stood when it was generated. Report ready Report register
- 1,280 assigned Copilot seats ready to activate and 160 unassigned seats was raised The finding was raised as new. The full record — the claim, the evidence and every change made to it — is on the insight itself. Recommendation Insight objects
- The estate moved 4 points up the Frontier Scale was raised The finding was raised as new. The full record — the claim, the evidence and every change made to it — is on the insight itself. Recommendation Insight objects
- 416 staff signed into unsanctioned AI apps in the last 30 days was raised The finding was raised as new. The full record — the claim, the evidence and every change made to it — is on the insight itself. Recommendation Insight objects
- Activate 1,280 Copilot seats ready to use was raised The finding was raised as new. The full record — the claim, the evidence and every change made to it — is on the insight itself. Recommendation Insight objects
- Monthly department chargeback — July 2026 is ready Generated by a monthly schedule and filed in the library. Its figures are frozen as they stood on the day it ran. Report ready Report register
The five categories, and how many of each happened
Counted across the same 30-day horizon as the feed above — before your own switches, which decide what you see rather than what occurred.
Scroll sideways for the remaining columns.
| Category | In 30 days | What it means |
|---|---|---|
| Action required | 0 | Something is waiting on a person: a chargeback request raised against a department budget and not yet decided, or a department that has crossed an overage threshold its own budget owner set. Both are events that already happened in a register — neither is a nag this page invented. |
| Report ready | 2 | A report finished and its figures were frozen — generated by hand, or by a monthly schedule. |
| Data issue | 0 | Something that should have produced a document did not: a report that failed with a reason, a report still generating long past the point where one should have finished, or a scheduled run that found nothing honest to freeze. |
| Recommendation | 4 | A finding raised against this organization moved — acknowledged, taken up, completed or dismissed. |
| Platform update | 0 | A configuration act was recorded against this organization in the operations register: money, licenses, access or settings. |
Where every item came from
Four registers, all of them ones other workspaces here already read. Nothing on this page is generated.
Scroll sideways for the remaining columns.
| Register | On this request | Events | If it did not answer |
|---|---|---|---|
| Leader-access requests | answered | 0 | |
| Report register | answered | 5 | |
| Report schedules | answered | 0 | |
| Insight objects | answered | 4 | |
| Operations register | answered | 0 | |
| Chargeback journey | answered | 0 |
Nothing here was sent to anybody
This surface is in-app because it is in-app. Aristo sent no email, posted no Teams message and pushed no notification for any row above — they are events read out of registers when you opened this page.
The one piece of outbound machinery this product owns is the weekly sponsor digest: an adaptive card, sent to the sponsors named in Settings, on a per-tenant send budget, behind the organization's quiet-mode gate. Carrying a report or a finding into it needs three things that do not exist yet — a card design for a report, a decision about whether a report competes with the daily send budget every other message is metered against, and an answer for what a person does with a card about a document they must leave Teams to open. None of them has been built, so none of them is promised here.