Audit log for admins
What a Customer's admins see of every call made in their Tenant, by people, keys and agents, and how they take it with them.
A Customer's owner and admin read every Action taken in their Tenant: who, for whom, through which Interface, and with what result. The screen reads the audit log, which is append-only and provable.
What each row holds
| Field | Example at Harbor Residential |
|---|---|
| When | 2026-10-22T12: |
| What | Lease.renew on Unit 5C, |
| By | Ines Duarte, or the Success Manager agent for its own calls |
| Via | app, api, mcp or cli |
| Key or session | The key's name, never its secret |
| Result | done, refused with the rule, or failed |
Refused calls are rows too. An admin sees the export a viewer tried, and the rule that stopped it.
Filter and follow
Filter by person, agent, Verb, record or date. Each row opens the record as it stood at that moment, and the record's own history lists every Action that touched it.
A Customer's agent calling through the API shows by name, with the person it acts for. So "who changed this rent" has one answer, whether a manager or an agent made the change.
Take it out
The owner exports the Tenant's log with Collection.export, once or on a schedule to their own warehouse. The log is hash-chained, so anyone holding a published root verifies it offline, without trusting Leaseline.