> 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/organization-administration/notifications.md).

# Organization notification settings

Set default notification preferences for all organization members and lock settings to enforce them, including the new in-app and email channels.

Organization admins and owners can control notification defaults for all members and optionally lock settings so members cannot change them.

Go to [Organization Settings > Notifications](https://app.cogram.com/dashboard/settings/admin/notifications).

## How it works

Each notification setting has two controls:

| Control           | What it does                                                                                             |
| ----------------- | -------------------------------------------------------------------------------------------------------- |
| **Active switch** | Sets the default on/off value for all members.                                                           |
| **Lock button**   | When locked, members cannot change the setting on their own. The lock icon shows "Locked" or "Unlocked". |

When a setting is locked at the organization level, it is also locked for group admins; they cannot override or unlock it.

## Tasks & approvals

These categories reach members in the [notification bell](https://docs.cogram.com/your-account/notifications.md) and by email. The **In-app** channel is always on; locking or disabling email never removes items from the bell. The **Email** column sets the org-wide default and can be locked:

| Category                 | Description                                                                                                                                          |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Task assignments**     | Email members when a task, action item, RFI, submittal, or change order is assigned to them.                                                         |
| **Approvals & requests** | Email members when someone requests access to a project they can grant access to. Access-request notifications go to organization admins and owners. |

## Email-only notifications

| Setting                        | Description                                                                                                                                                                                                                                               |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Post-meeting summary email** | Automatically send a summary email to the meeting host after a meeting ends.                                                                                                                                                                              |
| **Pre-meeting briefing**       | Send a briefing email before recurring meetings.                                                                                                                                                                                                          |
| **Shared meeting minutes**     | Email users a link to the draft meeting minutes when a colleague shares them. Only sent if the organization has enabled share-link emails to invitees under [Organization Settings > Meetings](https://app.cogram.com/dashboard/settings/admin/meetings). |
| **Meeting failure**            | Email users when Cogram is unable to join or transcribe a meeting.                                                                                                                                                                                        |
| **Added to project**           | Email users when they are added to a project.                                                                                                                                                                                                             |
| **Workflow reports**           | Email scheduled workflow reports to the recipients configured on each workflow.                                                                                                                                                                           |

## Locking a setting

Click the lock icon next to any setting to toggle between **Locked** and **Unlocked**. When locked:

* Members see the toggle grayed out with a lock icon and the message explaining who locked it.
* Group admins also cannot change or unlock the setting.

> **Note:** Group admins can independently set defaults and locks at the group level for their group members, as long as the organization has not already locked them. Open your group from [Group Management](https://app.cogram.com/dashboard/settings/group/all) and go to its **Notifications** tab.


---

# 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/organization-administration/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.
