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

# Notifications

Filed surfaces activity on your clients through in-app notifications. The notification bell is visible in the top navigation bar for all members.

## In-app notifications

In-app notifications appear in the bell icon in the top navigation bar. A badge showing the unread count appears on the bell. Clicking the bell opens the notification panel, which lists recent notifications with their category, the actor who triggered them, a description, and a timestamp. Unread notifications are shown in bold. A **Mark all read** action clears the unread state for all items.

**Walkthrough: open the notification panel**

1. Click the bell icon in the top navigation bar. The notification panel slides in from the right and lists recent notifications (category, actor, description, and timestamp), with unread items shown in bold. When you have no activity yet, the panel shows an empty state.

![The notification panel opened from the bell icon](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/notifications-panel/image1.webp)

2. When there are unread notifications, a **Mark all read** action at the top of the panel clears the unread state for every item at once.


---

# 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.filed.com/reference/workspace-and-settings/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.
