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

# Notifications & Alerts

> Get the right findings to the right people—via Slack, email, or webhook—as they happen or on a scheduled digest.

Notification rules let you route CraftCX findings to the people and systems that need them, without requiring everyone to log in and check the dashboard. You choose what triggers a notification, how often it's sent, and where it's delivered.

## Creating a notification rule

Go to **Settings → Notifications → Alerts** and click **Create notification rule**.

<Steps>
  <Step title="Name your rule">
    Give the rule a short, descriptive name so it's easy to identify in your list—for example, "High-severity incidents → #support-ops" or "Weekly AXIS digest to team lead".
  </Step>

  <Step title="Choose which events trigger it">
    Select one or more event types:

    | Event                 | When it fires                                                 |
    | --------------------- | ------------------------------------------------------------- |
    | **Incident detected** | A new policy violation or incident is created in CraftCX      |
    | **Low AXIS score**    | An [AXIS score](/features/axis-score) drops below a threshold |

    You can select multiple events for a single rule.
  </Step>

  <Step title="Set the delivery schedule">
    Choose how often notifications are sent:

    | Schedule             | What happens                                                              |
    | -------------------- | ------------------------------------------------------------------------- |
    | **Immediate**        | A notification is sent as soon as the event occurs                        |
    | **Scheduled digest** | Notifications are batched and delivered once per day at a time you choose |

    If you choose a scheduled digest, select the days of the week and the hour of delivery. The digest time uses your local timezone.
  </Step>

  <Step title="Add destinations">
    Add one or more places to deliver the notification:

    * **Slack** — select a connected Slack workspace and a channel
    * **Email** — enter an email address
    * **Webhook** — enter a URL to receive a POST request

    You can add multiple destinations to a single rule. For example, send a notification to both a Slack channel and an email address.
  </Step>
</Steps>

## Managing your rules

All your notification rules are listed in **Settings → Notifications → Alerts**.

### Enabling and disabling rules

Each rule has a toggle to enable or disable it without deleting it. This is useful when you want to pause alerts temporarily—for example, during a planned maintenance window.

### Editing a rule

Click **Edit** on any rule to update its name, events, schedule, or destinations.

### Deleting a rule

Click the actions menu on a rule and select **Delete**. You'll be asked to confirm before the rule is removed.

## Notification preferences

In addition to team-level notification rules, each team member can manage their own personal notification preferences in **Settings → Notifications → Preferences**. This controls how you receive in-app and personal notifications, separate from the shared rules above.

## Delivery destinations

### Slack

To send notifications to Slack, you first need to connect your Slack workspace via **Settings → Integrations**. Once connected, you can select any channel your Slack bot has access to when creating a notification rule.

### Email

Enter any valid email address. Notifications are sent from CraftCX and include a summary of the event and a link back to the relevant finding or incident in the dashboard.

### Webhook

Enter a URL that accepts a POST request. This is useful for routing notifications into tools like PagerDuty, Linear, Jira, or custom internal systems. The request body contains a JSON payload describing the event.

## Scheduled digests

Digest notifications batch everything that triggered the rule since the last delivery into a single message. This reduces notification fatigue for high-volume environments while still ensuring your team stays informed.

When setting up a digest, you can configure:

* **Days of the week** — choose any combination of weekdays
* **Hour of delivery** — select the time using your local timezone

<Tip>
  Digests work well for lower-urgency signals like AXIS score trends. Use immediate delivery for high-severity incidents where your team needs to respond quickly.
</Tip>

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How many notification rules can I create?">
    There's no hard limit on the number of notification rules. Create as many as you need to route different event types to the right audiences.
  </Accordion>

  <Accordion title="Can I send the same event to multiple destinations?">
    Yes. A single rule can have multiple destinations. For example, you can send an incident alert to a Slack channel and an email address at the same time.
  </Accordion>

  <Accordion title="Can different team members get different notifications?">
    Yes. Create separate rules for different audiences. For example, a rule that sends all incidents to a Slack channel for the whole team, and a separate rule that emails a specific manager only for high-severity incidents.
  </Accordion>

  <Accordion title="What does an immediate notification include?">
    Immediate notifications include a summary of the event—the incident title or the affected AXIS score—along with a direct link to the relevant record in CraftCX.
  </Accordion>

  <Accordion title="What does a digest notification include?">
    A digest summarizes all events that fired the rule since the last delivery: a count of new incidents or low-score events, a brief description of each, and links back to the dashboard.
  </Accordion>

  <Accordion title="Can I disable a rule temporarily without deleting it?">
    Yes. Use the toggle on each rule in the notifications list to disable it. Re-enable it at any time.
  </Accordion>

  <Accordion title="What timezone is used for digest delivery?">
    Digests are delivered at the hour you select, using your local browser timezone at the time you created or last edited the rule.
  </Accordion>

  <Accordion title="How do I connect Slack?">
    Go to **Settings → Integrations** and follow the Slack connection flow. Once your workspace is connected, Slack channels become available as destinations in any notification rule.
  </Accordion>
</AccordionGroup>

<CardGroup>
  <Card title="Incidents" icon="triangle-exclamation" href="/support-observability/incidents">
    Understand what triggers an incident notification.
  </Card>

  <Card title="Policy Monitoring" icon="shield-check" href="/support-observability/policy-monitoring">
    Learn how policy violations are detected.
  </Card>

  <Card title="Integrations" icon="plug" href="/integrations/overview">
    Connect Slack and other tools to your CraftCX account.
  </Card>
</CardGroup>