Your reads today8alert threshold 120
Tickets touched3every row carries one
Cross-tenant reads1a named capability, not a gap
Your own trail
Reads as well as actions. Append-only, and nothing here edits it.
| When | What | Target | Ticket |
|---|---|---|---|
| 14 Sep 13:36:00 | user.read | Adam Voss · DHM | 9104 |
| 14 Sep 13:28:00 | account.read | Account 81233 · DHM | 9104 |
| 14 Sep 13:21:00 | signal.read | Account 81233 · 40 rows | 9104 |
| 14 Sep 12:42:00 | impersonate.start | Adam Voss | 9104 |
| 14 Sep 12:42:00 | wallet.read | Adam Voss · DHM | 9104 |
| 14 Sep 11:42:00 | escalation.raise | Wallet credit · $29.00 | 9104 |
| 14 Sep 10:42:00 | settings.repush | Account 81204 | 9092 |
| 14 Sep 09:42:00 | terminal.restart | Account 81233 | 9104 |
| 13 Sep 13:42:00 | user.read | Lena Hoff · NSC | 9088 |
| 13 Sep 12:42:00 | crosstenant.read | Tenant NSC · 1 user | 9088 |
Why this page exists
The one panel where looking is an action
- Reads are audited in this panel and in no other. Unusual, and deliberate: this console’s risk is quiet browsing of other people’s finances, not a bad write. Opening a user, an account, a signal log or a wallet each writes a row.
- The trail protects you as much as the company. "Did somebody look at my account" is a question with an answer, and so is "did I". That is only true if you can read your own, which is why this page exists rather than the trail being invisible to the person in it.
- Cross-tenant read is a named capability with its own audit stream. Every other panel is tenant-scoped by a query filter; support cannot be, because an agent must open any tenant’s client to help them. Reading more than 120 customers in an hour raises an alert — a number, so you know where the line is rather than guessing.
- You see yours. Not anybody else’s, and nobody sees yours here but you and an admin. There is no route on this panel that returns another agent’s rows.