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

# Notifications

Portal notifications are configured in two places: an **SMTP provider** (the credentials for sending mail) under **Providers**, and **Notifications** (which use case gets routed to which provider) under its own top-level section.

## Adding an SMTP Notification Provider

Go to **Providers**, select the relevant Provider group, then open the **Notifications** tab — a category alongside Cloud, Kubernetes, Observability, Incident Management, Source Control, and GRC.

![Notifications provider tab, empty](/files/FgTraAXmMJtUJYRlRLjz)

Click **Add** and follow the same **Provider Details → Credentials → Scope** flow described in [Providers](/docs/armor/providers.md#adding-providers-and-defining-scopes). **SMTP** is currently the only notification provider type.

![Provider Details step — Type set to SMTP](/files/E9SY8DQ9TECtWe2BPSsC)

On the **Credentials** step, fill in:

* **Name\*** — a label for this credential
* **SMTP Host\*** — the mail server hostname
* **Port\*** — the SMTP port (commonly `587`)
* **From Address\*** — the address mail is sent from
* **Username\*** and **Password\*** — SMTP auth credentials

![SMTP credential fields filled in](/files/EgXWw3P5jmLvCryXBFks)

Finish the **Scope** step as with any other Provider, then attach it to the relevant Workspace(s).

![Attach Scope to Workspaces](/files/dADzro8D0TFEYWn6wwJY)

## Routing Notifications to a Provider

Go to **Notifications** in the sidebar. This page lists each notification **use case** and how many channels are configured for it.

![Notifications use case list](/files/nu3Y6zLYnq6XcT4jL43I)

Click a use case to open it, then **+ Add Channel**.

![Use case detail, no channels configured](/files/4y4tyyBWXjzChXOYsfr0)

For each channel, set:

* **Enabled** — toggle the channel on or off without removing it
* **From Identity** (optional) — overrides the SMTP provider's From Address for this use case
* **Provider\*** — the SMTP provider to send through

![Channel filled in with a provider and From Identity](/files/ZrYlkaugxBrJZjNcN0BU)

Click **Save**.

![Use case list showing 1 enabled channel](/files/ojKCGfmvhbxinOntUvoh)

{% hint style="info" %}
A use case with no enabled channel simply doesn't send anything — there's no default or fallback provider. Today there's a single use case, **New User Welcome**, sent automatically whenever a new user is created; more use cases will appear here as they're added, with no configuration needed to make them show up.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.duplocloud.com/docs/armor/additional-components/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.