> 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/my-alerts.md). # Your alerts Open **My alerts** to choose which notices reach you and through which channels in the current workspace. ## Choose your channels Review each notification type and its available Slack, Email or Text choices. Set the notices you want, then select **Save alerts**. A channel turned off for the workspace stays off even if you want it enabled personally. Ask an admin about [Workspace alerts](/settings/workspace-alerts.md) if a channel is unavailable. Slack notices require the correct Slack connection and member mapping. Text messages require the workspace's messaging setup and a usable phone number. Email depends on the recipient address and sending configuration. ## Separate alerts from meeting messages Personal alerts notify you about activity. [Meeting messages](/scheduling/messages.md) are configured on events and templates for hosts or guests. Changing your personal alert choices does not rewrite the guest's event reminders. Workflow **Notify in Slack** and **Notify by Email** steps are another separate path: their recipients are configured in the workflow. ## If a notice is missing Check the active workspace, notification type, workspace channel policy and connected identity. Confirm the underlying booking or assignment happened before changing notification settings. Use a controlled event when testing. Avoid enabling every channel just to investigate one missing notification. --- # 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/my-alerts.md?ask=&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.