> For the complete documentation index, see [llms.txt](https://docs.lossless.io/aegis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lossless.io/aegis/add-an-alert.md). # Add an alert Aegis alerts are issued through user notification channels based on triggers. Each trigger category offers unique parameters that enable users to fine-tune their alerts. To monitor multiple trigger categories simultaneously, you'll need to configure multiple alerts. ## Add an Alert To add an alert, users need to have already set up at least one notification channel. Jump back to [Add a notification channel ->](/aegis/add-a-notification-channel.md) Before proceeding further, users are also advised to familiarize themselves with Aegis triggers. Jump back to [Triggers ->](/aegis/triggers.md) ### Customize Trigger Users can customize certain alert parameters based on the selected trigger category. Users may opt to be notified when certain risk type(s) are detected or receive notifications about particular smart contract state changes and interactions. ### Select a Notification Channel Select the notification channel(s) where you wish to receive alerts for your selected triggers. Alerts can be configured to notify more than one person within your team or organization. --- # 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.lossless.io/aegis/add-an-alert.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.