Document AI Governance policy-change events in Activity logs (follow-up to #25239)
@dvdksn is already working on this.
Since Jun 4, 2026.
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 108
Description
Summary
Follow-up to #25239. That PR documents the sbx-side local audit log (sandboxd's JSONL records of policy decisions + session lifecycle, collected by SIEM tools). This issue tracks the separate, Hub-side audit surface: AI Governance policy-change events in Activity logs, which are already live but undocumented.
Background
Two distinct audit surfaces exist for AI Governance:
- Local audit log (sbx) — what a sandbox policy decided at runtime (allow/deny per request). Documented in #25239 at
content/manuals/ai/sandboxes/governance/audit.md. - Activity logs (app.docker.com) — who changed a governance policy in the Admin Console / via the Governance API. Served by the Docker Audit Logs API and shown in the Activity logs UI.
The governance events are confirmed live (seen in a test org), for example:
created governance policycreated/updated/deleted governance policy rule '<name>'set governance setting '<name>' from '<old>' to '<new>'
But content/manuals/admin/activity-logs.md currently only documents Settings Management "Policy created/updated/deleted" events — nothing for AI Governance.
What remains
- Add AI Governance events to
content/manuals/admin/activity-logs.md— a new subsection (or rows under Organization events) coveringgovernance.policy.create/update/delete, including thedatafields (org_uuid,policy_id,policy_type,rule_changes,settings_changes) andaction_descriptionexamples. - Verify the Hub API reference (
reference/api/hub,audit-logstag) lists thegovernance.*action types. This is generated/vendored, so a missing entry may need an upstream fix rather than a docs edit. - Cross-reference the two surfaces — once the Activity Logs section exists, link it and the sbx audit log page to each other (runtime policy-decision audit ↔ org-level policy-change audit), so readers don't conflate them.
References
- Field descriptions: https://github.com/docker/audit-log-helper/blob/main/docs/field_descriptions.md
- Docker Audit Logs API:
/reference/api/hub(audit-logs tag) - Local audit log page introduced in #25239
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.