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

# Workspace notifications

> Configure which events generate notifications and how they're delivered.

Admins configure workspace-level which events generate notifications and default channels. Each user can then customise their own.

## Workspace policy

<Steps>
  <Step title="Settings → Workspace notifications">Admin-only.</Step>

  <Step title="Global events">
    For each event type (deal won, invoice overdue, task assigned...):

    * **Always notify**: ignores user preferences
    * **User default**: user can disable
    * **Opt-in**: disabled by default, user can enable
  </Step>

  <Step title="Default channels">
    For new users, pre-selected channels:

    * Mobile push
    * Email
    * Slack (if integrated)
    * In-app
  </Step>
</Steps>

## Notifiable events

| Category        | Events                                         |
| --------------- | ---------------------------------------------- |
| **CRM**         | Deal created/assigned, stage changed, won/lost |
| **Tasks**       | Assigned, overdue, completed, comment received |
| **HR**          | Leave requested, approved, new employee        |
| **Finance**     | Invoice issued, paid, overdue                  |
| **Automations** | Workflow failed, webhook received              |
| **System**      | New Arya version, scheduled maintenance        |
| **Social**      | Mentions, bulletin reactions                   |

## Granularity

Each event can have specific rules:

<AccordionGroup>
  <Accordion title="Per role">
    Some events notify only certain roles. E.g. "Invoice > €10k overdue" → only CFO + Admin.
  </Accordion>

  <Accordion title="Per threshold">
    "Deal won" notifies sales team only if value > €5k.
  </Accordion>

  <Accordion title="Per conditions">
    "Task overdue" notifies only if priority = High or Urgent.
  </Accordion>
</AccordionGroup>

## Workspace quiet hours

Configure hours when workspace doesn't send notifications (respects work-life balance):

* **Weekends**: no non-critical notifications
* **Off-hours**: e.g. 19:00-08:00 weekdays
* **Holidays**: auto-silenced

`Critical` events bypass (e.g. broken workflow blocking invoicing).

## Notification templates

Customise notification messages:

<Steps>
  <Step title="Settings → Notifications → Templates" />

  <Step title="Pick event">E.g. "Deal won".</Step>

  <Step title="Edit template">
    * **Email subject**: `🎉 Deal {{deal.name}} closed won!`
    * **Email body**: markdown with variables
    * **Mobile push**: short (max 200 chars)
    * **Slack**: blocks supported
  </Step>

  <Step title="Preview">See render with sample data.</Step>
</Steps>

## Email branding

For outgoing emails:

* Workspace logo in header
* Brand colours
* Role-specific signature (e.g. "The Acme Corp team")
* Footer with useful links (FAQ, contacts)

## Slack / Teams integration

If your team uses Slack or Microsoft Teams as primary channel:

<Steps>
  <Step title="Connect integration">[Slack](/en/integrations/slack) or Teams.</Step>
  <Step title="Map events to channels">E.g. "Deal won" → #celebrations, "Task overdue" → #operations.</Step>
  <Step title="Routing rules">Exclude events that would flood channels (e.g. "task comment" → direct DM instead of channel).</Step>
</Steps>

## Monitoring

Dashboard **Settings → Notifications → Analytics**:

* Sent notification volume
* Email open rate
* Most-used channels
* Users with most silences (may be overwhelmed)

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can a user fully silence notifications?">Yes, but `Critical` events (admin-marked) can't be silenced.</Accordion>
  <Accordion title="How to avoid notification burnout?">Reduce notifiable events. Use daily digest instead of real-time for non-urgent events.</Accordion>
</AccordionGroup>