> 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/manage-your-personal-notifications.md).

# Manage your personal notifications

Some notifications are yours to control. The Notifications card on your Personal Settings page lets you choose which ones you receive and whether Essential emails you a digest, without affecting anyone else on your team.

Technician schedule-change notifications use a separate mobile preference controlled by your business's admin policy. See [Configure technician schedule-change notifications](/administration/settings/configure-technician-schedule-notifications.md).

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

## Email digest

Essential emails you a digest of the notifications and activity you choose. By default, this includes your notifications, such as teammate mentions, and business activity you have permission to view: quotes, invoices, jobs, customers, tasks, inspection reports, and inventory.

The email separates **Your notifications** from **Activity feed**, with record names, who made each update, and links back to Essential. It can contain either section or both. The digest is on by default and is sent only when there are new notifications or activity to include.

Visit activity in the same digest is grouped into one entry, with the job number, customer, property, and visit date. When the digest includes a Job Summary submission or update, that entry also includes **Tech Visit Notes** and related inspection-report activity. Repeated edits to the same report are combined, so the email count reflects the grouped updates. You can open the job in Essential for the full details.

Choose how often Essential sends the digest:

* **Off** — Essential does not email you notification digests. Your notifications still appear in Essential.
* **Every hour** — the default. Essential groups your notification emails into an hourly digest.
* **Every day** — Essential groups your notification emails into a daily digest.

To change the frequency:

1. Open **Settings → Personal Settings**.
2. In the **Notifications** card, select **Off**, **Every hour**, or **Every day** under **Email frequency**.
3. Click **Save**.

The change is not applied until you save it.

Your email frequency applies to both sections. Turning email **Off** does not change the notification bell or mark your Activity Feed as read. Re-enabling email starts fresh for activity, without emailing updates from the period when it was off.

## Choose which events you receive

**Notify me about** is one shared selection for your Activity Feed, notification bell, and email digests. The Activity Feed gear opens the same editable form in its dropdown. The notification bell gear opens Personal Settings. Your choices follow your account across devices.

Choose any combination of events. To receive only signed quotes, customer notes and paid invoices, select **Choose events**, click **Clear events**, then check **Signed quotes**, **Customer notes**, and **Paid invoices**. Click **Save**. Other activity and direct notifications stay off unless you select them too.

For your own selection:

1. Under **Notify me about**, select **Choose events**.
2. Check the types you want in each group. For example, turn off created invoices while keeping paid invoices. A group checkbox selects or clears the whole group.
3. Under **Direct notifications**, choose mentions, reminders, new service requests, report PDFs, purchase order updates, and accounting sync failures.
4. Turn off **Include my own activity** to skip changes you performed yourself.
5. Click **Save**.

**Customer notes** includes notes and timeline comments on customers and properties. **Paid invoices** means fully paid; select other invoice and payment types for partial payments. Leave **Include my own activity** on if manually recorded payments and notes you add should appear.

**All events** includes new types added in the future. With **Choose events**, new types stay off until selected. **Clear events** empties both in-app lists and stops digest emails. Record timelines still retain their history.

Email frequency is independent. With email **Off**, you can still edit your event choices and receive matching in-app updates. Turning email back on keeps those choices.

Saving event choices starts a fresh digest period: earlier updates are not emailed. Changing only hourly/daily frequency keeps the current period. Saving does not mark hidden events as read. Saving from the Activity Feed dropdown or Personal Settings updates the same account preferences. There is no separate temporary category filter.

When more than 100 activity updates match your choices and permissions in one period, Essential sends one short **Activity summary** with a link back to Essential. Excluded activity does not count toward the limit. Updates covered by the summary are not carried into later emails in batches of 100. Selected direct notifications keep their details in the same email.

## New service requests

Website intake form and Customer Portal requests notify back office users by default. Clicking the notification opens the request and its submitted answers.

To turn them off, select **Choose events**, uncheck **New service requests** under **Direct notifications**, and click **Save**. This hides that type in the bell and excludes it from digest emails.

## Good to know

* These preferences are per-user, so your choices do not change what your teammates receive.
* New hires are notified automatically; there is no list for an admin to keep up to date.
* It follows your account, so it applies wherever you sign in.
* Turning **New service requests** off hides existing request notifications and stops new ones in the bell and digest. Related activity can still appear in the **Activity feed** section if you have access. A shared-inbox email copy of each submission is set up separately, business-wide, under Settings → Customer Experience → Intake Form → Notifications — see [Get notified about new service requests](/administration/settings/get-notified-about-new-intake-form-submissions.md).
* The digest's **Your notifications** section only includes notifications you haven't yet read in Essential.

## Related guides

* [Get notified about new service requests](/administration/settings/get-notified-about-new-intake-form-submissions.md)
* [Reset or change your password](/administration/settings/reset-or-change-your-password.md)
* [Choose your default home page](/administration/settings/choose-your-default-home-page.md)
* [Choose your appearance (Light or Dark)](/administration/settings/choose-your-appearance-light-dark-or-system-theme.md)


---

# 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/manage-your-personal-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.