> For the complete documentation index, see [llms.txt](https://docs.scaleflex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleflex.com/portals/portal-settings/notifications.md).

# Notifications

Choose who hears about it when a Portal is published.

When you publish a Portal, the people who rely on it don't necessarily know. **Notifications** sends them an email.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FwPQbMvzkDS4yctIbmGkh%2Fimage.png?alt=media&#x26;token=2191a13d-e4ef-4d48-aace-9e46ae2ebe3f" alt=""><figcaption><p>The <strong>Notifications</strong> page, where the recipient list is kept.</p></figcaption></figure>

## Set it up

1. Open **Notifications**.
2. Turn on **Enable notifications by default**.
3. Add recipient email addresses. **Press Enter to add each address.**

With it on, every publish offers to notify those people, and you can add a message saying what changed. With it off, publishing is silent.

{% hint style="info" %}
Turning notifications on requires at least one recipient — *Add at least one recipient, or turn notifications off.*
{% endhint %}

## Who to include

The people who act on the Portal's contents rather than everyone who can open it: the agency waiting for new artwork, the sales team waiting for a price list. A notification that arrives for every typo fix gets filtered, and then the one that mattered is missed too.

You can always publish without notifying — the choice is offered each time.
