> For the complete documentation index, see [llms.txt](https://docs.sectoral.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sectoral.xyz/using-sectoral/alerts.md). # Alerts Alerts are how Sectoral gets in touch with you. Anything happening on your account is surfaced when it matters, so you never have to rely on checking in yourself. *** ## Alert types | Type | Raised when | | -------- | ----------------------------------------------------------------------------- | | Transfer | The status of a payment you sent or received changed (settled or failed) | | Policy | A spend policy on one of your agents blocked a payment or needs your approval | | Security | Someone signed in, or a key or wallet on the account changed | | System | A platform announcement not tied to any specific payment | Every alert is labeled with its type, so you can tell at a glance which ones need action (typically Policy) and which are just for your information. *** ## Managing alerts * Unread alerts show a solid dot on a highlighted background * Opening an alert marks it as read * **Mark all read** marks every alert as read in one go * Use the **All** and **Unread** tabs at the top to switch views *** ## Choosing what you hear about Under the list, **Notification preferences** gives each rule its own toggle. Turning a toggle off means no new alerts of that type will be created. Alerts you have already received stay visible, and nothing about how your account behaves changes. This is worth stressing: muting Policy alerts leaves your agent's spend policy exactly as strict as before. Sectoral simply stops telling you each time the policy blocks or holds something. The policy is enforced regardless of whether you are notified. To learn how enforcement works, read [Spend Policy Engine](/ai-agents/policy-engine.md). *** ## Read on * [Spend Policy Engine](/ai-agents/policy-engine.md) * [Account Settings](/using-sectoral/settings.md) --- # 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.sectoral.xyz/using-sectoral/alerts.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.