> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Settings & Notifications

> The General, Notifications and Danger Zone areas of a team's Settings — team logo, name and phone number, muting non-critical notifications, escalation automations, and how to leave or delete a team.

## Overview

Every team has a **Settings** area, reached from **Settings** in the sidebar. It opens on a left-hand sub-navigation with seven tabs and a **Settings** heading that repeats across every tab. This page covers the **General** tab, the **Notifications** tab, and the **Danger Zone** card that sits at the bottom of General — the rest of the tabs are documented on their own pages, linked below.

***

## The Settings Tabs

| Tab               | What it covers                                                                          | Documented on                                              |
| ----------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| **General**       | Team logo, team name, team phone number, and the Danger Zone (leave or delete the team) | This page                                                  |
| **Members**       | Inviting people, pending invitations, roles, removing members                           | [Inviting & Managing Members](/team/members)               |
| **Billing**       | Your plan and subscription                                                              | [Managing Your Subscription](/billing/subscription)        |
| **Invoices**      | Invoice history and downloads                                                           | [Payment Methods & Invoices](/billing/payment-methods)     |
| **Usage**         | Wallet and minute usage history                                                         | [Usage History](/billing/usage)                            |
| **Notifications** | Muting non-critical notification types, and a link to escalation automations            | This page                                                  |
| **API Keys**      | Generating and managing API keys                                                        | [API Keys & Authentication](/api-reference/authentication) |

General opens by default when you click **Settings**.

***

## General

The General tab is three cards for the team's identity, followed by the Danger Zone.

### Team Logo

The **Team Logo** card holds an image uploader. Click the circular placeholder (or the current logo) to choose a new image — any image file type is accepted, one at a time — or click **Clear** to remove the current logo. The uploader's own labels read "Upload a Profile Picture" / "Choose a photo to upload as your profile picture." even though the card above it is titled **Team Logo**.

### Team Name

The **Team Name** card holds a single text field, pre-filled with the current name, and an **Update Name** button that stays disabled until you change something. A new name must satisfy all of the following:

| Rule           | Detail                                                                                                                        |                             |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
| Length         | 2–50 characters                                                                                                               |                             |
| Characters     | No special characters — letters, numbers and spaces only (punctuation such as \`! @ # \$ % ^ & \* ( ) + = \[ ] { } ; : ' " \\ | , . \< > / ?\` is rejected) |
| Reserved words | Can't be `settings` or `billing` (case-insensitive)                                                                           |                             |
| Uniqueness     | Can't match the name of another team you own                                                                                  |                             |

Saving shows *Updating Team...* then *Team successfully updated*, and reloads the Settings page.

### Team Phone Number

The **Team Phone Number** card holds a phone input (defaults to an Australian number format) and an **Update Phone Number** button, disabled until the field is dirty. The number must be a valid phone number in international format (e.g. `+61123456789`) and can't already be in use by another team account — Voxworks checks for a duplicate before saving and rejects the update if one exists.

### Owner-Only Editing

All three General cards — logo, name and phone number — can only be changed by the team's **primary owner**. If anyone else submits a change, it's rejected with: *"Only the team owner can update these settings. Please contact your team owner to request changes."* See [Roles & Permissions](/team/roles-permissions) for how the primary owner differs from an ordinary Owner-role member.

***

## Notifications

<Note>
  Notifications — the bell, the Notifications tab, and the underlying Notification Created automations — are currently in **beta, available to selected invites only**. If your team is interested in joining the beta, reach out to the Voxworks team.
</Note>

The **Notifications** tab is two cards: **Emergency alerts** and **Muted events**.

### Emergency Alerts and Escalation Automations

Email and SMS escalation for critical events runs through your team's automations, not through a separate settings form — the **Emergency alerts** card explains this and links straight to them. Every team starts with two system automations, **Emergency SMS alerts** and **Emergency email alerts**, both triggered by critical notifications. You edit their recipients, messages and conditions in the automations editor; they can be disabled but not deleted.

Click **Manage escalation automations** to open [Automations](/automations/overview) directly. See [Notification-Based Triggers](/automations/notification-triggers) for how a **Notification Created** trigger can filter on severity and event type — the same mechanism the system escalation automations use.

### Muting Notifications

The **Muted events** card lists the non-critical notification types you can turn off for the team, each with its own checkbox:

| Event                    | Label               |
| ------------------------ | ------------------- |
| `call.completed`         | Call completed      |
| `call.failed`            | Call failed         |
| `batch.started`          | Batch started       |
| `batch.completed`        | Batch completed     |
| `dispatch.delayed`       | Dispatch delays     |
| `automation.dead_letter` | Automation failures |

Checking an event mutes it: Voxworks stops creating notifications of that type for the team, so they no longer appear in the bell, don't trigger any **Notification Created** automation, and aren't counted toward the unread badge. Click **Save settings** to apply your changes — you'll see *Saving…* while it processes, then *Notification settings saved*.

**Critical notifications can't be muted.** Emergencies, failed batches and exhausted credits always create a notification regardless of what's checked here — those are the events the Emergency alerts card's escalation automations exist to catch.

<Note>
  Saving muted events is restricted to the team's primary owner (or a super admin) — the same restriction as the General tab's cards. Anyone else who tries to save sees the request fail.
</Note>

***

## The Notifications Bell

The bell icon in the top bar shows a red badge with your unread notification count (capped at "99+") — the badge pulses if any unread notification is critical. Clicking the bell opens a popover listing your recent notifications, newest first, each with a severity icon, a one-line summary, and a relative timestamp (e.g. "5 minutes ago", hovering shows the exact date and time).

* Clicking a notification marks it read and, if it links to something — a call, a batch — navigates you there.
* **Mark all as read** appears in the popover header whenever you have unread notifications.
* A **critical** notification that hasn't been acknowledged shows an **Acknowledge** button; once acknowledged it shows *Acknowledged*, who acknowledged it, and how long ago.
* Muted event types never appear in this feed, regardless of severity display — see [Muting Notifications](#muting-notifications) above.

***

## Danger Zone

The bottom of the General tab carries a red **Danger Zone** card — *"This section contains actions that are irreversible"* — with one of two actions depending on your role:

* **Delete Team** — shown only to the team's primary owner (or a super admin). Permanently deletes the team and everything in it, gated behind an emailed verification code.
* **Leave Team** — shown to everyone else. Removes only your own membership; the team continues for everyone else.

Both actions, the confirmation steps, and what happens to your data are covered in full on [Deleting an Account or Team](/account/deletion) — this page only tells you where to find them.

***

## Next Steps

* [Inviting & Managing Members](/team/members) — the Members tab: invites, pending invitations, roles and removal.
* [Roles & Permissions](/team/roles-permissions) — how the primary owner differs from an Owner-role member.
* [Deleting an Account or Team](/account/deletion) — the full leave and delete flows, including the email verification step.
* [Automations Overview](/automations/overview) — where escalation automations and every other automation live.