> For the complete documentation index, see [llms.txt](https://docs.useglade.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useglade.org/guides-for-the-app/notifications.md).

# Notifications

Glade uses notifications to tell you when something on your account needs your attention. You don't have to keep checking the app to stay informed.

***

## Kinds of notification

| Kind     | You get one when                                                                         |
| -------- | ---------------------------------------------------------------------------------------- |
| Transfer | A payment you sent or received has settled or failed                                     |
| Policy   | One of your agents' spend policies has blocked a payment or is waiting for your approval |
| Security | There's been a sign-in, or a key or wallet on your account has changed                   |
| System   | Glade posts a platform-wide announcement unrelated to any particular payment             |

Each notification shows its kind as a label. That makes it easy to separate the ones you need to act on (usually Policy) from the ones that are only informational.

***

## Working through the list

* A notification you haven't read has a filled dot and a highlighted background.
* Opening one marks it read.
* **Mark all read** clears every unread notification at once.
* The **All** and **Unread** tabs at the top switch between the full list and just the unread ones.

***

## Turning kinds on or off

Below the list, **Notification preferences** has a separate toggle for each rule. Switching one off stops new notifications of that kind from being created. Anything already in your list stays there, and your account keeps working exactly as before.

Be clear about one thing in particular. If you turn off Policy notifications, your agents' spend policies are not relaxed in any way. Glade just no longer tells you each time a policy blocks or holds a payment, and enforcement carries on regardless. For how enforcement works, read [Spending rules](/agents/spending-rules.md).

***

## Related guides

* [Spending rules](/agents/spending-rules.md)
* [Preferences](/guides-for-the-app/preferences.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.useglade.org/guides-for-the-app/notifications.md?ask=<question>&goal=<user_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.
