> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/technical-docs/notifications/notifications-ui.md).

# Notifications UI

When an account has notifications enabled, a notification bell will appear in the left-nav section, just to the the right of the Daasity logo. If there are new notifications, a red badge on top of the bell will appear containing the count of unsolved notifications.

## Account Status Page

<figure><img src="/files/ANGIb71HQr9171KjGjtb" alt=""><figcaption></figcaption></figure>

## Notifications List

When clicking on the bell, a list of notifications will be displayed. The example below shows an authorization failure that happened on a Criteo integration.

<figure><img src="/files/kbyH30kpALGNmBOD0YJd" alt=""><figcaption></figcaption></figure>

### Integration Page

Clicking on the call to action button (e.g. Authorization Failure button) in the notification will take you to the integration show page. The integration page will display an appropriate message related to the failure.

<figure><img src="/files/beY9OScdKr9D2nSQyjVA" alt=""><figcaption></figcaption></figure>

## Integration List

The integrations list page has been enhanced to highlight integrations that have errors/failures. The new section will always appear at the top as "Failed Integrations". That section will display the integration card with the appropriate error message on it.

<figure><img src="/files/qoVvJyfirovprXU4zWoJ" alt=""><figcaption></figcaption></figure>


---

# 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://help.daasity.com/technical-docs/notifications/notifications-ui.md?ask=<question>&goal=<endgoal>
```

`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.