# Send event notifications

> Source: https://elaichi.ai/docs/guides/settings/notifications/

Tell Elaichi where to announce things that happen in this organization — someone joining, a connection going stale, a role changing. Each destination picks its own events, so an on-call channel and a compliance mailbox can watch different things.

**Where to find it:** **Settings → Notifications**

You need **Manage notifications** (`notification:manage`) to add, edit, or delete destinations. **View notifications** (`notification:view`) is enough to see the list. Unlike [Logging](/guides/settings/logging), notifications are available on every plan.

## Destination types

| Type | What you provide | Goes to |
| --- | --- | --- |
| **Slack** | An incoming webhook URL | The channel that webhook belongs to |
| **Email** | One or more addresses | Each address listed |

## Add a destination

1. Open **Settings → Notifications** and choose **Add destination**.
2. Name it something you will recognise in a list — the name appears on the delete confirmation and in test results.
3. Pick **Slack** or **Email**, then supply the webhook URL or the address list.
4. Select the events to send. Nothing is sent until at least one is chosen.
5. Save, then use **Send test event** to confirm it arrives.

**You'll know it worked when:** the test lands in the channel or inbox, and **Last test** shows a timestamp on the row.

## Events you can subscribe to

**Connections** — connection needs reauth, connection disconnected.

**Members and teams** — member joined, member removed, member roles updated, team member added, team member removed.

**Access and security** — invite sent, invite revoked, API token created, API token revoked, SSO connection created, SSO connection updated, MFA disabled.

**Governance** — role created, role updated, role deleted, restriction updated.

## Turning one off

Each row has an **Active** toggle. Switch it off to stop delivery while keeping the destination and its event selection — useful during noisy migrations.

:::callout{type="warning"}
Deleting a destination is not the same as deactivating it. Delivery stops immediately **and** the stored secret — the Slack webhook URL — is permanently deleted. Re-adding it later means fetching a fresh webhook from Slack.
:::

## Good to know

- Events are organization-scoped. A destination only ever reports on the organization it was created in.
- Editing a Slack destination leaves the existing webhook in place unless you enter a new one, so you can rename or re-scope events without re-pasting the URL.
- Notifications announce events as they happen. For a durable, queryable record, forward to your observability stack with [Logging](/guides/settings/logging) instead — the two are complementary.

## Related

- [Forward audit events](/guides/settings/logging)
- [Read the audit log](/guides/governance/read-the-audit-log)
- [Verify a domain](/guides/settings/verify-a-domain)