> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-email-notifications.md).
# Sealights Email Notifications
SeaLights provides ability to receive notifications on builds reported to the Dashboard. These notifications are available on email.
Notifications are triggered according to rules defined including your criterias:
* Application or Branch
* Build status (success/failure)
* Quality Gates or Quality Risks
* etc
***
Email notifications are available out-of-the-box with your Sealights account.
In order to add email recipients to notifications per the rule defined, please add all the email addresses to the **‘Who’ section** and press ‘**Save**’.
You’ll receive an email notification from **Sealights <>** like below:
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-email-notifications.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 `automate deployments from our CI pipeline` 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.
