What you get notified about
Dashboard notifications appear for these campaign events:
Schedule created
Schedule updated
Publish succeeded
Publish failed
Rollback applied
Rollback failed
Notifications show the campaign name, version, actor, time, and a quick link to the item.
Device health alerts live on the Device health page. This page covers campaign notifications only.
Who receives notifications
Admins and Managers receive dashboard notifications by default.
Viewers can see status in the UI but do not receive action notifications.
Where notifications appear
Bell icon in the CMS header lists unread and recent items.
Campaign list shows state badges and next start time.
Campaign detail shows the latest event with a link to the audit log.
Notification behaviour
Real time delivery when actions complete.
De-dupe and grouping prevent repeated spam for the same event.
Mark as read from the bell menu or from the campaign detail.
The audit trail
The audit trail records who changed what and when for every campaign. It includes:
Content edits in Singles and Collections
Target changes and device selection
Schedule creates and edits
Publishes, failures, and retries
Rollbacks, archives, and restores
Version diffs and validation results
How to view the audit trail
Open a campaign.
Click Audit to see the timeline.
Filter by event type, actor, date range, or version.
Click any entry to see field-level diffs against the previous version.
Export
Export the audit log to CSV from the Audit view.
Share Preview links for reviewers to check the live render without granting edit access.
Permissions
Admins and Managers can view the full audit log and receive notifications.
Viewers can view version history and diffs.
Authors see audit for their Experiences and Releases. Repo and branch data is visible to Authors only.
Best practices
Use clear campaign names that include release and date for easier audits.
Schedule ahead and watch for a Publish succeeded notification before store open.
When something fails, open the audit entry, review the error details, then republish.