> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/alerts-and-notifications.md). # Alerts & Notifications Learn how Brava reports transaction, recommendation, and risk events. ## Alerts and Notifications Brava tells you when something has happened to your capital, or is about to. ### What you are told about **Transactions.** A transaction settled, or did not. Notifications carry the bundle, so you can go straight to the record. **Recommendations.** Something Brava or your agent thinks is worth acting on. **Risk.** A change in the risk profile of something you hold. The notification centre filters by these three. ### Where they appear The bell in the header carries unread counts. Where something needs attention rather than awareness, the count is marked. Notifications deep-link. Selecting one opens the thing it is about: the transaction, strategy, or pool. ### Notifications are not the record A notification tells you something changed. **Transactions** holds what actually happened. Where the two disagree, or a notification never arrived, trust **Transactions**. ### Preferences Delivery and channel preferences sit in workspace settings, per workspace. A person in several workspaces is notified according to each. --- # 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.brava.finance/platform/alerts-and-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.