# OMNICHANNEL_ALERTS_ENABLED

Canonical page: https://docs.ovok.com/settings-and-features/settings/omnichannel-alerts-enabled

Turns on [Omni-channel alerts](/signals/with-ovok/omni-channel-alerts). Ovok runs your [rule](/signals/with-ovok/routing-rules) on each alert event Signals sends and tells the people it names, by push and email.

| | |
| --- | --- |
| Type | Boolean setting |
| Change with | `PUT /v1/project/settings/OMNICHANNEL_ALERTS_ENABLED` |
| Who can change it | Project admin |
| When unset | Off |
| Needs | A Signals tenant of the project's own |
| When off | Ovok tells nobody. Signals still sends its alert events to your own webhooks. |

```bash
curl -X PUT 'https://api.sandbox.ovok.com/v1/project/settings/OMNICHANNEL_ALERTS_ENABLED' \
  --header "Authorization: Bearer ${OVOK_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data '{"enabled": true}'
```

## What turning it on does [#what-turning-it-on-does]

Ovok subscribes to the tenant's alert events. Turning it off removes the subscription.

The setting does not write a rule. Until you save one, nobody is told.

## Gotchas [#gotchas]

- **No rule, no messages.** Check `GET /v1/omnichannel-alerts/rules` after turning it on.
- **Map the email templates.** `ALERT_NOTIFICATION` and `PATIENT_ALERT_NOTIFICATION` go out through your [email templates](/email-templates/map-templates).
- **Shared Signals tenants are not supported.** The project needs a tenant of its own.

## Related [#related]

- [Omni-channel alerts](/signals/with-ovok/omni-channel-alerts)
- [Routing rules](/signals/with-ovok/routing-rules)
