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

# Notifications

**Settings → Notifications** (under **Personal**) controls how TestVibe tells you about test runs, generations, load tests, and other activity — through the in-app header bell, browser alerts, and outbound channels like email, Slack, Google Chat, and Microsoft Teams.

## Open notification settings

1. Open **Settings**.
2. Under **Personal**, select **Notifications**.

## Channels

Each channel decides where notifications are delivered and, per category, whether you get **All**, **Failures** only, or **Off**.

| Channel                               | Delivers to                                    | Categories                                                                                              |
| ------------------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| In-app & browser                      | The header bell, plus opt-in OS/browser alerts | Test runs, Generations, Load tests, Runner questions, Invites & members, Billing & credits, Automations |
| Email                                 | Your account email (or a custom address)       | Test runs, Generations, Load tests                                                                      |
| Slack / Google Chat / Microsoft Teams | An incoming-webhook URL you paste              | Test runs, Generations, Load tests                                                                      |

The **In-app & browser** and default **Email** channels are always present and cannot be removed (you can turn categories off). Added channels start at **Failures** only. Use **Send test** to verify a webhook, and the **Browser alerts** toggle to opt into OS notifications (these fire only when the TestVibe tab is in the background).

## Mattermost (project-scoped)

Mattermost works differently from the per-user channels above: it's configured once per **project**, not per person, so the whole team shares one channel. Set a **`MATTERMOST_WEBHOOK_URL`** project secret (a self-hosted Mattermost incoming-webhook URL) from the project's env/secrets panel, and TestVibe posts a summary there whenever a run, generation, or load test finishes. An optional **`MATTERMOST_NOTIFY`** variable controls which outcomes post — `all` (default) or `failures`; set it to `off` to disable posting without removing the webhook. See [Add API keys and secrets](/workspace/add-api-keys-and-secrets.md).

## The header bell

The bell in the header shows an unread count and a dropdown feed of recent activity, with a live **In progress** section listing runs, load tests, and generations happening right now. Click an item to jump to its run, generation, or load-test details.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/account-settings/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.