Backed by: the control plane’s connection listing, the audit trail’s access history and allowed calls, and this dashboard’s own roster of your team. Scopes: connections:read, and audit:events:read as well for a date. Plan: Team.
What it answers
Who could reach customer data, when, and what they did with it.
Two answers, each a table: who can reach this environment now, and who could on a date. Access is what each connection was granted and used, scope kinds are the columns, and roles and permissions is what a role may do.
The pane sits in the rail’s Compliance group, after Access, when your Worker declares its connection listing. It reads GET /control-plane/connections and our own roster of your team, and for a date it also reads the audit trail. Every answer is dropped with the screen, like every other pane.
Rows, columns and cells
Rows are people and connections. Columns are the six scope kinds: reads, writes, sends, charges, deletes and credentials. Every cell says one word:
| Cell | What it means |
|---|---|
| Can | For a connection, its grant holds a scope of that kind. For a person, their role holds that power and this dashboard’s connection is granted a scope of that kind: both gates, and neither stands in for the other |
| Through an agent | A person who reaches it only through an agent or script whose connection names them as its principal |
| Cannot | Nothing on either path reaches it |
| Not recorded | The trail cannot show it either way. Only a date says this |
People are every member of your team, with their role, and every principal who is not, who reaches only through what they authorized. Connections are every connection the listing holds, with its actor kind, its principal and its purpose; this dashboard’s own is marked, and a revoked one or one whose keys have expired says so.
Now
Today’s table reads the listing alone, and answers as soon as the pane opens. Its grants are the ones your Worker enforces on each connection today.
On a date
Choose a range, and the table is rebuilt as of its first day. It replays the trail backwards from today’s listing, through every member, connection and key change from that day to now, so a date always reads the listing too.
- Never can where the trail cannot show it. A connection removed since may have been revoked by then, the trail records no key that ended before the date, and no key change after it proves a key was live on it. So a removed connection, one revoked since, one whose keys have expired, and one known only from the trail read not recorded for what they were granted. So does a change that did not record what it changed from.
- Some dates attest nothing at all, and say why: a date older than the trail keeps, a Worker that does not state how long it keeps it, more changes since than one page holds, or a change that named no connection.
- Roles are today’s. Your team’s changes are on our trail, not your Worker’s, so a person who joined after the date is left out and one who has left since is not shown.
- Each agent and script carries its allowed calls over the range, with the date of the last one. They are counted from one page of 100 each, and where there were more the pane says the count is a floor. Every other connection, this dashboard’s own included, says its calls were not counted rather than none.
In a report
Both are questions a report can name: Access attestation, now and Access attestation, on a date. Each section draws its table and exports it as JSON, and the dated one answers for the report’s range.
On Free and Solo
The pane is drawn locked, and says what Team buys. The same listing reads from pithy dashboard connections on any plan, and from your Worker’s API.
When it cannot answer
It sends nothing it would be refused. When this connection is not granted connections:read, or audit:events:read for a date, the record names the scope instead. Scopes is how to add one. When our roster cannot be read, the table says nobody’s reach through this dashboard is shown, rather than showing none.