> ## Documentation Index > Fetch the complete documentation index at: https://docs.thepublive.com/llms.txt > Use this file to discover all available pages before exploring further. # Notifications and audit trail > Which emails each workflow event sends, and what is recorded for every stage change. Every stage change sends an email to the right people and leaves a permanent record. This page covers both. ## Availability This feature is available on the **Custom Enterprise** plan only. To enable it for your workspace, contact [support@thepublive.com](mailto:support@thepublive.com). ## Email notifications Workflows sends **email only**. There are no in-app notifications. Recipients are worked out automatically, so there is nothing to configure beyond optional **Additional notification recipients** on a stage. ### Who is emailed For each event, the recipients are: * everyone who can act at the stage the entry has arrived at * the assignee, if there is one * the author A stage can also name **additional recipients**. They are told but are not expected to act. Use this for cases like letting Marketing know when content clears Legal. Recipients are de-duplicated. Nobody receives two copies of one event, and nobody is notified about their own action. ### Events A workflow has no fixed forward or backward path: a stage's **Next stages** can point to any other stage. Every move uses the same **Move to** dialog, with the same optional note. One move produces exactly one event, whatever its destination. | Event | Who is emailed | Subject | | - | - | - | | Entry arrives at a stage for the first time | Actors at the new stage, the assignee, and additional recipients for the stage | `Review needed: ` | | Entry reaches a stage for additional recipients only | Additional recipients | `FYI: reached ` | | Entry returns to a stage it has already been at | The author, everyone who moved it on since it was last at that stage, and additional recipients for the destination stage | `Sent back: ` | | Entry assigned to someone | The new assignee | `Assigned to you: ` | | Stage overridden | Actors at every skipped stage, and the author | `Review skipped: ` | | Entry published or scheduled | The author | The existing publish or schedule email, unchanged | Each email has one button that opens the entry. Where a note or reason was entered, it is included in the email. People who approved an entry earlier are **not** emailed when it eventually goes live. ## Audit trail Every stage change is recorded permanently and cannot be edited or deleted. Each record holds: * who acted, and their role at the time * when it happened * the entry * the stage it moved from and the stage it moved to * the note or reason, if one was entered * whether the move was an override Records survive the deletion or renaming of the stage or workflow that produced them, and still name the stage as it was. The same records appear in two places: * the entry's **History** timeline, for the people doing the work. See [Review and move content](https://docs.thepublive.com/dxp/documentation/content-workflows/review-and-move-content.md#the-timeline). * [Audit Logs](https://docs.thepublive.com/dxp/documentation/concepts-features/audit-logs.md), for compliance and investigation, alongside every other audited action. Retention follows your workspace's audit retention policy. ## Next steps > [card] [Audit Logs](https://docs.thepublive.com/dxp/documentation/concepts-features/audit-logs.md) > > See everything Publive DXP records across your workspace. > [card] [Content Workflows overview](https://docs.thepublive.com/dxp/documentation/content-workflows/overview.md) > > Back to the concepts. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.