Learn · Audit & evidence
The workspace audit log
Who changed a role, a key, or a setting inside your work area.
Checked against the product on · written for people who run the account
This is the answer to the audit-log question on a vendor security questionnaire. It is readable by the admins of the work area it covers, and it is append-only.
console.dmzagent.com/settings/audit
Prove
Audit log
1All actorsLast 30 daysExport CSV
2
| Time | Who | Action | Target |
|---|---|---|---|
| 12:31 | dana@ | Role changed to admin | sam@ |
| 11:02 | dana@ | API key created | ck_test_…9b17 |
| 09:44 | sam@ | Rule pack pinned | Support conduct 1.1.2 |
3Append-only. Secret material is stripped before an entry is written.
Open Settings, then Audit log, and set the window.1
Read the rows.2
Each one names the actor, the action, and what it acted on.
Read the redaction line.3
| Action | Recorded when |
|---|---|
| Role changed | Someone is invited, promoted, demoted, or removed. |
| Key created | An API key is made. |
| Key revoked | An API key is revoked. |
| Setting changed | A work-area setting is edited. |
| Rule pack pinned | A pack is installed, moved to a new version, or removed. |
- The actor email is kept on the row, so the trail stays legible after a person leaves the account.
- Secret material is stripped before an entry is written, so a key value never reaches the log at all.
- There is no edit and no delete. Erasing data is a separate flow with its own record.