> For the complete documentation index, see [llms.txt](https://docs.jcore.io/clarity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jcore.io/clarity/alarms/configure/audience.md). # Audience {% hint style="warning" %} **Note:** even if you have selected a user to receive notifications, whether they actually receive email or text notifications depends on how they have configured their [contact preferences](/clarity/contact-preferences.md). {% endhint %} Only users and groups in the **Audience** list for an alarm will see it. If **Notify** is turned on for a user or group, they will receive notifications for alarm events; if Notify is turned off, they will only see the alarm state within Clarity.

To add another user or group to the audience, search for them in the **Add people and groups** field:

Then click on the user to add them. To remove a user or group, click the

icon next to them:

If you want to turn notifications on or off for a user or group, click the switch in the **Notify?** column:

However, note that your changes won't be saved until you click **OK** in the alarms table:

--- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.jcore.io/clarity/alarms/configure/audience.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.