Reporting as a live view
A report opens as rows you can inspect, not as a file you must order before you can see the answer. The live view is paginated, sortable and scoped to the reader. Export and scheduling remain available as the closure of looking.
One evaluator for view and file
Saved views and reports share the configured-view evaluator. The selected kind, filter, columns, reader scope and masking rules determine both what appears on screen and what can be exported. Reporting does not maintain a second query that can silently drift from the view.
The columns and sort a person picks on a list or report are saved to their account, so they follow them to another device or browser; "Reset to default" in the Columns menu puts both back.
The current reporting vocabulary includes identity-governance rows such as grants, decisions and effective permissions. Object references in cells carry their identifiers so supported rows can drill into the governed object.
A catalogue grouped by question
Since 6 November 2026 the report catalogue is grouped by the question a business reader asks: who has access to what, why someone has it, what changed, what to clean up, whether reviews and approvals are on track, and what proves it to an auditor. Report names and columns are in plain words ("Admin rights", "Unused access", "Accounts nobody owns", "Leavers who still have access", "People without a manager", "Decisions made"), what a report asks for is a sentence ("Optional: a system", "Last 92 days"), and exported headers and values are plain words too. Internal ids are no longer default columns; they can still be picked. The BI feed of a list sits under "For BI tools".
Standard reports added in this round:
- How is the access review going? One row per reviewer per review, with a pace verdict against the due date. A reviewer who is behind or has not started gets a Send reminder button that reminds them about that review only (administrators and business administrators; a team or role queue has nobody to remind).
- Approvals waiting, and for how long: open approval tasks, oldest first, escalations marked.
- Conflicting access: the stored separation-of-duties findings, with held conflicts labelled rather than hidden.
- What can one person access?: pick a person; their grants.
- External people and when their access ends: sponsor, organisation, end date and days left, with ended-but-still-active flagged.
- Why does this person have this access?: one row per right, with how it was obtained, who asked, who approved in order and the reason.
- Access added and removed: the audit chain for a period, by whom or by which rule.
Reader scope and masking
Opening a report applies the reader's scope. A manager and an administrator can open the same definition and legitimately see different rows. A restricted reader does not gain broader access because somebody else created or scheduled the report. An empty report under a limited scope says that its rows are limited to what the reader may see, rather than "No matching records".
Field visibility also applies to exports. A masked column is removed from the file rather than merely hidden in the browser.
Export caps before the click
Before export, the platform evaluates the current result and reports:
- the number of rows selected;
- the cap for each available format;
- whether the current result fits;
- whether a format would truncate.
Viewing is paginated rather than capped. Export limits control file generation, not what an authorized reader may inspect.
Schedules and delivery
A saved report can retain its export and schedule workflow. The report definition still owns delivery configuration, while the live view owns inspection. Point-in-time output remains evidence of what the evaluator returned for that run; it is not a permanently live link.
"As it stood on" and what it can say
A report can be read as it stood on an earlier date. The answer is rebuilt from the recorded history of grants being made and revoked, plus the grants a sync observed. It states how complete that history is. If the date is before the record starts, the report says the record starts on a given date and that the answer is unknown, not that nothing was held; an incomplete history reads "unknown, not empty".
Rows name things as people do: the "Who has access to what" report shows the account's native name and the system's name, not internal keys or ids.
An application's access can be exported as a CSV file from its page. A role with the tenant-wide export right exports any application. An owner exports only an application they own, or one in whose catalogue they own an entitlement; for any other application there is no export button and the export answers as not found. Every export is recorded in the audit trail with the authority it used.
Conditions you pick, not type
A report condition takes its value from the real options where there are any: a system by its name, a status from its list, a person, an entitlement or an account found by search, several at once for "is any of" and "is none of". The condition stores the identifier and the summary sentence shows the name. Free text stays for "contains" and for a column without a list, which today includes the five org dimensions. The options follow the reader's scope and field visibility: a hidden field is not offered, and a restricted reader gets no data-backed list outside identities they may see.
What some catalogue reports leave out
- Identities without a manager lists people only. Non-human identities have an owner, not a manager, and appear in the non-human inventory instead.
- Grant reports skip a grant that is not in the target when its account was retired: nobody holds that access and nothing will create it. A grant still in the target on a retired account stays listed. The list, the export and a scheduled run agree.
- Privileged access names the account on every row, so admin rights on an account no identity is linked to read as that account. A saved copy of the report keeps the columns it was created with; add "Account" through Columns there.
-
Lifecycle / JML carries the numbers of the Lifecycle page: joiners, movers and leavers per type with how many were on time, the open exceptions longest overdue first, the slowest events, and the people in scope split by status with non-human identities as one separate number. An empty section says so in words.
-
My team's access is the reader's team only, also for a manager who owns a system; ownership does not widen it.
- Decisions made shows outcomes (approved, rejected, expired) by default, with who it was for, what access and who asked; superseded, skipped and withdrawn are one filter away.
- Accounts nobody owns leaves out terminated accounts and accounts waiting to be deleted, as Access posture, Account rules and the Accounts list do.
- Unused access counts only systems that report usage; elsewhere there is no usage to judge.
- High-risk identities without a set threshold lists the riskiest tenth of active people, instead of a fixed score that may never be reached.
- Admin rights also lists entitlements with a high or critical risk level.
- Leavers who still have access lists only people a source system says left (not manual identities), and says per grant whether the leaver grace still keeps it or has ended.
Object owners open Reports with the narrow report:read_owned permission, which does not
open the tenant-wide evidence PDFs.
What a report cannot see
A standard report about leavers, privileged access, dormant accounts or orphan accounts shows a strip above the list when some systems cannot answer its question: the systems left out per gap (a system that reports no usage cannot answer "dormant", for example) and the systems whose last sync failed. Each gap links to where it is fixed. The run keeps that answer as it was when it ran, also in its audit event, and the run detail says "Systems left out: n". The strip is shown to tenant-wide readers; a reader with a limited scope does not get it, because coverage is a fact about the whole tenant. Access posture has the same view per system on its What we can see tab: what is seen, linked to people, understood and used.
The files
A report's PDF, composed or table, comes from one renderer: a header card, a strip with the date it stands on (in the tenant's time zone), the filter in words, the tenant and the scope, then the tables with values by column type ("Yes"/"No", dates, "Never", "No identity linked"), and page numbers. A table over six columns prints in landscape. The Excel export has a bold header row, fitted widths and a filter; CSV is unchanged.
Current limits
- The live report catalogue, open-as-list experience and export/schedule closure are shipped.
- A universal live configuration rail is not yet present on every report view.
- Summary mode is not yet a general reporting primitive.
- Do not infer that a delivered file remains current after its run.
- Delivery history should be read per recorded run; do not claim transparent resend or exactly-once delivery.
See workbench lenses, evidence and signing and API reference.