---
title: "Choose your notifications"
description: "Choose which personal alerts reach you by email, push, or Slack DM. Turn off a whole channel or category, or mute an individual event where available."
---

> Full documentation index: https://docs.alpacax.com/llms.txt

# Choose your notifications

<span id="notification-preferences" />

# Choose your notifications

Open **Notification preferences** from the account menu at the bottom of the left sidebar. The page shows the **Server alerts** card first, then **Browser notifications**, then the grid of notification categories and channels.

The grid lets you turn off a category's channel or a whole channel. Your choices only affect delivery the workspace already offers; they cannot enable an unavailable channel. Browser push also needs permission in this browser.

## Server alerts

The **Server alerts** card shows three severity rows. Its two switches change the same settings as the matching category and channel in the grid:

- Critical alerts can send email and post to the team's Slack channel. **Email me critical threshold alerts** controls your threshold-alert email in the **Server** category. A rule that sends no email still sends none when this switch is on.
- Warning alerts can post to the team's Slack channel and appear in the hourly summary email to admins. **Email me the hourly summary** controls the **Open alert digest** category's email channel.
- Info alerts appear only in the bell. This row has no switch.

Slack delivery is set per rule, not per person. Select **Open alert rules** to review those settings. A switch is shown off, grayed out, and locked when you cannot change it, for example because all Server email is off or the workspace requires that channel. A disabled channel cannot be enabled here; restore its parent category first when that is what turned it off.

If event-level controls are unavailable, the card shows the three severity descriptions without switches.

The card's app address ends in `#server-alerts`, so a link to it scrolls directly to the card. To change alert conditions, see [Configure metric alerts](/use/metrics/rules/). To mute one server, see [Monitor server status](/use/servers/monitor/#mute-a-server).

<span id="turning-off-a-single-event" />

## Turn off a single event

Expand a category to see its events. Supported category and channel combinations, such as email for **Server**, show a switch for each event. Other cells list the events they cover without individual switches.

Turning off a category's channel turns off and locks its event switches. An event you had separately disabled keeps the **Also off on its own** tag; restoring the category does not restore that event. When the category is on but some events are off, a tag such as "3 off" shows their count. Select it to expand the row.

To restore a whole channel, select the unchecked box in that column's header. This restores every category and every individually disabled event in the column to its default.

Accounts without personal notification settings see **This account has no personal notification settings.** instead of the grid.

## Slack DM

The **Slack DM** column controls direct messages from the Alpacon Slack app. It stays dimmed, with no switches, until you can receive them:

- If the workspace hasn't connected Slack, the dot in the column header reads **Needs admin setup**. A Superuser connects it; see [Connect Slack](/integrate/slack/).
- If Slack is connected but your Slack account isn't linked to your Alpacon account, the dot reads **Connect to receive**. Ask a Superuser to [link your account](/integrate/slack/#link-members-to-slack).

Some direct messages are sent whatever this column says: a work session request you can approve yourself, which reaches you first ([details](/reference/notifications/#when-you-can-approve-your-own-work-session-request)), and the decision on your sudo request.

## Check your changes

A switch stays in place once Alpacon saves your choice. If a change is refused, the page shows a message and leaves the previous setting in place.

## When email stops arriving

Alpacon stops sending email to addresses on its email provider's suppression list. An address can be added when email delivery fails permanently or its owner reports a message as spam. Alpacon checks the list daily, so the restriction may appear after the next daily check. Other channels, including Slack and the in-app feed, and your ability to sign in are not affected.

In the notification grid, the email column shows **Connect to receive**, just as it does when your account has no email address. You cannot restore delivery by turning notification settings back on.

To receive email again, change and verify your account email to a different address that is not on the suppression list. Email becomes available again after your account change syncs to the workspace. If you need to keep using the same address, contact [support@alpacax.com](mailto:support@alpacax.com).

<span id="notifications--webhooks" />
<span id="notification-delivery" />
<span id="what-triggers-a-notification" />
<span id="in-app-notifications" />
<span id="server-disconnection" />
<span id="direct-logins" />
<span id="metric-alerts" />
<span id="open-alert-digest" />
<span id="work-session-expiry" />
<span id="approval-requests-in-a-work-session" />
<span id="when-you-can-approve-your-own-work-session-request" />
<span id="session-risk-analysis" />
<span id="channels-and-where-theyre-configured" />
<span id="webhooks" />
<span id="who-can-configure-what" />
<span id="plan-availability" />
<span id="manage-from-the-cli" />
<span id="self-hosted-deployments" />
<span id="related-docs" />

For the events available to each channel, see [Notification reference](/reference/notifications/). For workspace webhook delivery, see [Webhook notifications](/integrate/webhooks/).

Source: https://docs.alpacax.com/use/settings/notifications/
