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

# Notification bell

Use the notification bell to stay on top of task assignments and project access requests, and act on them without leaving your current page.

The notification bell in the header collects what needs your attention in Cogram, for example a task assigned to you, or a request to join a project you manage. You can act on many notifications directly from the bell.

## The notification bell

Select the bell in the header (the top row that runs across the content area) to open your notifications. A badge on the bell shows how many notifications you haven't dealt with yet.

Each notification shows what happened and when. Selecting a notification takes you to the related item; for example, a task notification opens that task on the project board.

Opening the panel does not clear the badge. The badge clears as you deal with items:

* Acting on a notification (for example, approving an access request) clears it.
* Opening the related item (from the bell, from the email, or by navigating there yourself) clears the notification for it.

When there is nothing left, the panel shows "You're all caught up."

## What arrives in the bell

| Notification             | When you receive it                                                                                                                                                                                                                                                                                       |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Task assignments**     | A task or action item on a project board, or an RFI, submittal, or change order, is assigned to you.                                                                                                                                                                                                      |
| **Approvals & requests** | Someone requests access to a project you can grant access to (organization admins and owners).                                                                                                                                                                                                            |
| **Mentions**             | Someone @mentions you in a [project chat](https://docs.cogram.com/projects/project-chat.md) channel, or in an [internal comment](https://docs.cogram.com/contract-admin/internal-comments.md) on an RFI, submittal, change order or transmittal. Selecting the notification opens that message or record. |

All three also send an email by default. You can turn the email off per category: select **Notification settings** at the bottom of the panel, or see [Notification preferences](https://docs.cogram.com/your-account/notifications-1.md). Other Cogram notifications (post-meeting summaries, meeting failure alerts, and similar) are email-only today.

## Approve or decline an access request from the bell

When someone requests access to a discoverable project, organization admins and owners receive a notification with inline actions.

1. Select the bell to open your notifications.
2. On the access request, choose the role to grant from the dropdown (Lead, Member, or Viewer; Lead only if your organization has that role turned on).
3. Select **Approve** to grant access, or **Decline** to reject the request.

The requester is notified of the outcome by email, and the notification clears for everyone who received it. If a colleague resolves a request first, it disappears from your bell too.

To review all requests in one place, admins can open the full request list under [Organization Settings → Projects](https://app.cogram.com/dashboard/settings/admin/projects?tab=request-access).

## Troubleshooting

**A notification email arrived, but the bell shows nothing**

* Likely cause: someone already resolved the item, or you already visited it. Both clear the notification.
* Fix: nothing to do; the item itself remains available (for example, the request list under Organization Settings → Projects).

**You expected an access-request notification but didn't receive one**

* Likely cause: access-request notifications go to organization admins and owners.
* Fix: check your role with your organization admin.

**Notifications older than about three months are gone**

* Notifications are a short-lived feed and are removed after 90 days. The underlying items (tasks, requests, meetings) are not affected.

## Next steps

* [Notification preferences](https://docs.cogram.com/your-account/notifications-1.md): choose where each category reaches you
* [Projects](https://docs.cogram.com/projects/projects.md): project access and discoverability


---

# 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.cogram.com/your-account/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.
