Auditing
The page-admin Auditing nav item currently opens the Notification Events workspace for outbound customer communication and delivery-attempt inspection.
This guide is based on application/frontend/src/pages/admin/NotificationEvents.jsx.
What the auditing screen covers
The current screen is focused on outbound notification activity, not every admin mutation in the product.
It supports:
- browsing recent notification events
- filtering by event key
- filtering by delivery channel
- filtering by delivery status
- opening one event to inspect its delivery attempts
That makes it most useful when a team needs to understand whether a communication was created, queued, delivered, suppressed, or failed.
Event list and filters
The current filters support:
- event key such as
incident.updated - channel such as
email,webhook,sms,push, orrss - status such as
queued,sent,delivered,failed,retrying, orsuppressed
Each event row shows:
- event key
- severity
- entity type and entity ID
- creation timestamp
Delivery attempt inspection
Selecting an event opens the attempt list for that event.
The current attempt view shows:
- channel
- destination
- delivery status
- attempt number
- created timestamp
This is the part of the screen that answers questions like "did the email send?" or "was this notification retried?"
Event summary and payload details
For the selected event, the screen also shows a summary that can include:
- actor type and actor email
- auth method
- API-token hint
- Slack user ID
- action and resource identifiers
The payload is rendered as JSON, and if a magic link is present the UI includes a copy action for it.
Treat copied payloads and magic-link values as sensitive delegated-access material. Share them only through the same channels you would trust for any other time-limited access token.
Plan behavior
The current screen is gated behind audit-log support.
In the current UI, workspaces without that feature see a plan notice instead of the event inspector.