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

# Alerts

> Raise instant alerts, such as fire evacuations or welfare checks, that ping phones and show an in-app banner.

Alerts are for urgent, time-critical situations: fire evacuations, fire drills, site emergencies, welfare checks, or anything else your organisation configures. Raising an alert immediately notifies the audience on every channel they have enabled: phone push, email, and an in-app banner for anyone signed in on the web. The banner stays until the alert is resolved.

Alerts are separate from broadcasts. They are designed to be raised in two taps. Phone push for alerts deliberately bypasses quiet hours.

## Who can use alerts

* **Trigger alerts**: org admins and management roles (for example managers and duty managers) can raise and resolve alerts. Access is controlled by the **Trigger alerts** permission under **Roles & permissions**.
* **Manage alerts**: org admins can configure alert types and recipient groups with the **Manage alerts** permission.

## Raising an alert

1. Open **Alerts** in the admin sidebar (under Operations).
2. Tap the alert type, for example **Fire evacuation**.
3. Choose the audience: **Everyone in the organisation** or a recipient group.
4. Adjust the message if needed (it is prefilled with the type's default message) and press **Send alert now**.

Everyone in the audience is notified according to their personal alert channel settings. Delivery does not depend on who is clocked in. Signed-in web users see the banner straight away (including via realtime updates).

## Where people are notified

Each person can choose channels under **Settings → Notifications → Organisation alerts**:

* **In-app banner**: top of Campsite while signed in on the web
* **Phone push**: Campsite mobile app devices
* **Email**: their work email address

All three are on by default. Turning a channel off only affects that person.

## Resolving an alert

Active alerts appear at the top of the Alerts page. Press **Resolve** when the situation is over; the banner disappears for everyone. The person who raised an alert can always resolve it.

## Alert types

Admins define the one-tap options staff see. Each type has:

* a **name** (for example Fire drill or Site emergency)
* a **severity** (Critical, Warning, or Info) which sets the banner colour
* a **default message** that prefills when the alert is raised

If you are starting from scratch, use **Add starter types** to create a sensible default set (fire evacuation, fire drill, site emergency, welfare check).

## Recipient groups

Groups let you alert a specific set of people instead of the whole organisation, for example a welfare response team for a vulnerable person situation. Create a group from **New group**, add members, then pick that group as the audience when raising an alert. Only group members are notified and only they see the banner.

## History and delivery

The Alerts page keeps a history of every alert: who raised it, the audience, when it was resolved, and delivery counts for push, email, and in-app.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.