> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assuric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notify stakeholders of updates

> Update a published document and notify the stakeholders who hold it.

<Note>
  **Quick summary**

  * Updating a document on your Trust Centre and notifying the people who hold it are separate steps.
  * You can't send notifications until your Trust Page has a privacy notice URL.
  * Subprocessor changes must be notified. Hazard log updates are your call.
</Note>

The steps below also apply when a [published hazard log](/clinical-safety/sharing-and-publishing) changes.

```mermaid theme={null}
flowchart LR
  A["Approve new version<br/>(Trust page resource ticked<br/>in Republish options)"] --> B[Notify subscribers]
```

## Before you can notify anyone

Your Trust Page needs a privacy notice URL before you can send any notification. You're the controller for those emails, so recipients need somewhere to read how you handle their address.

<Warning>
  Set this up before the day a document changes. Finding out mid-send delays the update.
</Warning>

## Ship the updates

<Steps>
  <Step title="Approve the new version and republish it">
    Approve the new version in **Documents**. When you approve it, or send a controlled document for review and approval, [*Republish options*](/documents/versions-and-version-history#republish-options) lists the resource under *Trust page resources*, ticked.

    * Leave the resource ticked to move it to the new version once approved, or untick it to keep the old version on your Trust Centre.
    * Republishing keeps the resource's label and description. To change them, or to pick a different version later, click **Edit Resource** in the resource's options.
  </Step>

  <Step title="Renew expired access first">
    Expired contacts won't get the update. To include them, renew their access in bulk before you send.
  </Step>

  <Step title="Notify key stakeholders">
    * Open the resource's options, click **Send Notification** and pick who to notify of the change.
    * The list shows who has access, who's opted out of updates and whose access has expired.
    * Requesters opt in or out when they request access, so you don't set that for them.
  </Step>
</Steps>

<Tip>
  **What we recommend**

  * Update your Trust Centre when your release notes go out, so customers' governance teams don't have to email you for the paperwork.
  * Notify on significant changes to your hazard log or safety case, not every minor version, or people stop reading.
  * Always notify subprocessor changes. They're required.
</Tip>

## Related articles

<Columns cols={2}>
  <Card title="Access requests and who can see what" icon="eye" href="/trust-centre/access-control">
    Expiry dates, pre-approvals and who gets notified of requests.
  </Card>

  <Card title="Trust Centre FAQ" icon="circle-question-mark" href="/trust-centre/faqs">
    Quick answers to the things customers ask us most.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.