> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/control-what-your-team-is-notified-about.md).

# Control what your team is notified about

Decide whether your back office users get the Activity Feed and activity emails, and which events they can receive. Admins always get everything.

> **Where to find it:** Settings → Team → Team Notifications

You need the **Manage Roles & Permissions** permission to see this page. The default Back Office Admin role has it.

## Who this applies to

Team Notifications applies to everyone who can't manage roles and permissions. In this guide they are called back office users. It never limits anyone who holds **Manage Roles & Permissions**.

A user also needs the **View Activity Feed** permission for the feed and its emails. See [Roles and permissions](https://learn.withessential.com/administration/settings/roles-and-permissions.md).

## Choose what back office users can receive

1. Open **Settings → Team → Team Notifications**.
2. Under **Activity Feed and emails for back office users**, select one:
   * **Off** — the default. Back office users don't see the Activity Feed, their email digests leave out activity, and they don't get signed quote alerts.
   * **All events** — back office users can get every event, including new types added in the future.
   * **Choose events** — back office users can get only the events you select.
3. Click **Save changes**.

Nothing changes until you save.

## Choose the exact events

With **Choose events**, check the events back office users can get. A group checkbox selects or clears the whole group. **Select all events** and **Clear events** change every group at once.

The **Quotes** group has two signed-quote choices:

* **Signed quotes they created or sent** alerts each person only about the quotes they created or last sent. It appears in their notification bell and is emailed within a few minutes.
* **All signed quotes** shows every signed quote in the business in their Activity Feed and activity emails.

Select only **Signed quotes they created or sent** to give back office users that alert without the Activity Feed. The feed appears only when you select at least one other event.

New event types stay off until you select them. If you switch to **Off** or **All events** and back, your chosen events are kept.

## What stays the same

* Mentions, timeline reminders, new service requests, and other notifications addressed to one person are not affected. They still reach the notification bell and email digests at every setting.
* Each person can still turn off events and change their email frequency in Personal Settings. They can narrow what you allow, but they can't add to it. See [Manage your personal notifications](https://learn.withessential.com/administration/settings/manage-your-personal-notifications.md).
* Record timelines still show their full history.

Saving a change starts a fresh digest period for back office users, so earlier activity is not emailed. Turning on signed quote alerts applies to quotes signed after you save.


---

# 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://learn.withessential.com/administration/settings/control-what-your-team-is-notified-about.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.
