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

# Set up notifications

> Choose which events message your clients, which alert your team, and on which channel — all set once for the whole workspace.

DMLY sends messages automatically when things happen in your workspace. Some of those messages go out to a contact over WhatsApp, SMS or email. Some go to your team. Some are alerts that only ever appear inside DMLY.

All of it is controlled in one place, by an admin, for the whole workspace.

<Note>
  There is no per-user notification preference. Whatever an admin sets here applies to everyone and to every contact. A user's own profile controls their language, timezone and sign-in — not what DMLY sends. See [Profile](/account/profile) and [Security](/account/security).
</Note>

## Who can change them

Notification settings live in **Workspace Settings → Settings → Notification settings**.

The link to Notification settings sits in the admin-only **Workspace Settings** area, so in normal use only an admin reaches it. See [Roles and permissions](/account/roles-and-permissions).

## The two tabs

<Columns cols={2}>
  <Card title="Client & staff messages" icon="paper-plane">
    Messages that leave DMLY — WhatsApp, SMS or email — and land with a contact or a member of your team.
  </Card>

  <Card title="In-app alerts" icon="bell">
    Alerts that stay inside DMLY. Nothing here is ever sent to a client. See [Inbox notifications](/inbox/notifications).
  </Card>
</Columns>

That split is the one to keep in your head: **Client & staff messages** costs you a WhatsApp send and reaches a real person's phone. **In-app alerts** only ever reaches your own team, in the app.

## Customer-facing or team-facing

On the **Client & staff messages** tab, each card is one event and the cards are grouped under four headings. Each heading tells you who is on the receiving end:

* **Client notifications** — go out to the contact.
* **Staff notifications** — go to the staff member concerned.
* **Other notifications** — go to your team: the admin, receptionist or scheduler-type members rather than the staff member on the booking.
* **Finance notifications** — invoice sent, payment receipt, payment failed and renewal reminder all go out to the contact.

Each event is a card with a master toggle. The channel checkboxes — **Email**, **SMS** and **WhatsApp** — appear inside the card once the event is switched on, so you can send an event over WhatsApp only, or over WhatsApp and email, or turn it off entirely. WhatsApp is the one to lead with; leave the others off unless you have a reason.

## Turn a notification on

<Steps>
  <Step title="Open the settings">
    Go to **Workspace Settings → Settings → Notification settings**.
  </Step>

  <Step title="Pick the tab">
    **Client & staff messages** for anything that leaves DMLY. **In-app alerts** for the alerts your team sees in the app.
  </Step>

  <Step title="Switch the event on">
    Find the event's card and turn on its toggle. The channel checkboxes stay hidden until you do.
  </Step>

  <Step title="Tick the channel you want">
    Tick **Email**, **SMS** or **WhatsApp** — whichever you want the event delivered over.
  </Step>

  <Step title="Check the WhatsApp template">
    A WhatsApp notification is carried by an approved WhatsApp template. Ticking **WhatsApp** reveals a **WhatsApp template** dropdown inside the card. It opens on the default option — labelled **Default template** followed by the template's own `dmly_` name — with an **Approved**, **Pending** or **Rejected** badge beside it. The alternatives in the dropdown are your approved templates. See [Message templates](/broadcasts/message-templates).
  </Step>

  <Step title="Save">
    Press **Save** in the page header. Nothing is stored until you do, and your changes are lost if you navigate away first.
  </Step>
</Steps>

The page states it plainly: **These settings apply to every contact in this workspace.** There is no per-contact exception and no opt-out list here.

## If a notification doesn't arrive

<Accordion title="Nothing sent, or sent on the wrong channel">
  Work through it in this order:

  * The event is switched on, and the channel is ticked, on the **Client & staff messages** tab — and you pressed **Save**.
  * The channel itself is connected — a WhatsApp notification needs a connected WhatsApp number. See [Connect WhatsApp](/channels/whatsapp).
  * The WhatsApp template it uses is approved by Meta. An unapproved template means no send. See [Message templates](/broadcasts/message-templates).

  If all three check out, see [Messages not sending](/troubleshooting/messages-not-sending).
</Accordion>

## Next

<Columns cols={2}>
  <Card title="Team members" icon="users" href="/account/team-members">
    Invite the people who receive staff notifications.
  </Card>

  <Card title="Roles and permissions" icon="shield-halved" href="/account/roles-and-permissions">
    Who can reach Workspace Settings in the first place.
  </Card>
</Columns>