> For the complete documentation index, see [llms.txt](https://docs.r.xyz/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.r.xyz/main/bug-bounty/organizations/bb-settings/email-notifications.md). # Email Notifications The Email Notifications settings in the Remedy Bug Bounty platform allow you to control the types of emails you receive. Here’s how to configure them: #### All Report Thread Emails Select this option if you wish to receive email notifications for all activities related to report threads. This includes any updates, comments, or changes made within the report thread. Recommended For: Team members who want to stay fully informed about all ongoing report activities. #### Confirmed and Escalated Reports Emails Only Choose this option if you prefer to receive email notifications only for reports that have been confirmed or escalated by Remedy triagers. This setting minimizes the number of emails by filtering out updates from non-escalated and rejected reports. Recommended For: Team members who prefer to focus on high-priority reports and avoid cluttering their inbox with less critical updates. --- # 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.r.xyz/main/bug-bounty/organizations/bb-settings/email-notifications.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.