> For the complete documentation index, see [llms.txt](https://docs.mansafi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mansafi.xyz/everyday-use/alerts.md). # Alerts Alerts is the direction MansaFi reaches out to you: whatever is happening on the account, raised at the moment it matters, so checking manually is never the only way to find out. *** ## What fires | Type | Trigger | | -------- | ---------------------------------------------------------------- | | Transfer | A payment you sent or received changed status — settled, failed | | Policy | An agent's spend policy blocked something or wants your approval | | Security | A sign-in, key change, or wallet change on the account | | System | Platform notices unattached to any particular payment | Each alert wears its type, so a glance is enough to tell action (Policy, usually) from information. *** ## Working the list * Unread entries carry a filled dot and a lifted background * Opening one marks it read * **Mark all read** clears the lot * The tabs at the top switch between **All** and **Unread** *** ## Preferences Beneath the list, **Notification preferences** exposes every rule as an independent switch. Switching one off stops future alerts of that kind from being raised. It hides nothing already delivered, and it alters no behavior whatsoever. That last point deserves emphasis: silencing a Policy alert does not relax your agent's spend policy by a cent. It only stops MansaFi from mentioning when the policy did its job. Enforcement runs whether or not anyone is watching it. [Policy Engine](/agents/policy-engine.md) covers how that enforcement actually works. *** ## Continue * [Policy Engine](/agents/policy-engine.md) * [Settings](/everyday-use/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.mansafi.xyz/everyday-use/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.