Audit trails — resource change history + the Recents screen
Use D.Hub's *Recents* screen and per-resource change history to run the *who · what · when* 4-point audit pattern.
Once permissions and policies are set, the next operational agenda is tracking what actually happened. This lesson covers D.Hub's two audit surfaces — the Recents screen and per-resource change history — and combines them into a 4-point audit pattern.
Recents — the time-axis audit surface
The Recents menu in the lower left sidebar shows every change across every resource in reverse chronological order. Collection · dataset · code · pipeline · dashboard · ontology · agent · policy — any create · modify · delete · permission change lands as one line.
Each row carries 4 fields.
- Who — The user who made the change
- What — The target resource (name + kind)
- When — UTC timestamp + a human-readable N minutes ago indicator
- How — Change type (create · modify · delete · grant permission · revoke permission)
Top filters narrow by user, resource kind, and time range.
Per-resource change history
For the same information from a single resource's vantage, open the resource detail's upper-right ⋯ menu → Change history. Every change to that resource shows in reverse chronological order. Who changed this dataset's schema and when, who granted permissions on this collection — the full history of one resource on one screen.
The change history for policy resources is also the entry point to revert to N versions ago (Lesson 5).
Audit scenarios — the 4-point pattern
Four kinds of audit requests come up most often. Here's how to handle each via Recents + change history.
Scenario 1: What did user X do today?
- Recents → User filter for X, time range today.
- See the distribution by change type on one screen. For unusual patterns (e.g. unintended dataset deletions), click the row to drill into the change details.
Scenario 2: When was dataset D's schema last changed?
- D detail → Change history → Modify filter.
- Check the user · timestamp of the most recent schema change row.
Scenario 3: I want collection C's permission-grant history for the last month
- C detail → Change history → Grant permission · Revoke permission filter, time range Last 30 days.
- All grant/revoke history shows on one screen. The primary source for compliance reporting.
Scenario 4: Yesterday's change to policy P landed wrong — I want to see the pre-change state
- Portal Settings → Policies → P detail → History tab.
- The policy body as of yesterday shows read-only. The Revert button restores that version (Lesson 5).
Self-check
- Open Recents and confirm you can see every change you made today.
- Open the Change history tab on an arbitrary dataset and confirm you can view N versions ago.
- Narrow the permission grant history on a collection via filter.
Wrap-up
If you made it this far, you've handled D.Hub's admin cycle end-to-end — permission model → SSO/provisioning → groups → FGAC → policy operations → audit trails.
Two next directions:
- Agent Builder Path — When you introduce AI automation, the permission and policy patterns from this Path stack directly on top of AI tool calls. Admins naturally sit at the safety gate of AI adoption.
- Workshop: refund-approval — Walk the permission · policy · reviewer separation pattern of HITL agents through a real scenario.
Great job.