> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/settings/workspace-alerts.md).

# Workspace alerts and failure notices

Admins choose the channels and defaults available to workspace members. Open **Workspace alerts** where enabled.

## Set the workspace defaults

Review the event types and Slack, Email or Text channels. Choose which channels are allowed and which choices new members start with. Configure the workspace Slack destinations when the controls are available, then save.

Members can refine their personal choices within this policy. A workspace-disabled channel cannot be enabled by a member's My alerts selection.

## Configure workflow failure notices

In notification settings, review the workflow-error Slack destination and **Email administrators**. A failure notice should reach someone who can inspect the run and correct its connection or configuration.

Choose a channel your team actually monitors. An error channel is not a substitute for handling expected outcomes, such as No match or Not booked, on the workflow canvas.

## Check delivery

Connect [Slack](/integrations/slack.md) and map the relevant members before relying on Slack DMs. Connect [Twilio](/integrations/twilio.md) before using SMS. Verify the sending setup for email.

Generate a controlled event, inspect its actual result and check the chosen destination. Some settings appear only for enabled features or admin accounts.

See [Your alerts](/settings/my-alerts.md), [Workflow logs](/workflows/logs.md) and [Meeting messages](/scheduling/messages.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/settings/workspace-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.