# Teams and roles

A team holds everything you monitor in Spectate: monitors, hosts, domains, alerts, incidents and status pages. Each team has its own plan, its own members and its own settings. Each member of a team has one role, and the role decides what the member can do in that team.

## Teams

When you sign up, Spectate creates a team for you, named after you, for example "Jane Doe's Team". You are its owner. You can rename it under **Team → Settings**.

You can be a member of more than one team, for example one per company or customer. Every team has a separate plan and a separate bill. Data never moves between teams.

### Create a team

1. In the dashboard, go to **Team**.
2. Select **Create team**.
3. Type the **Team name**.
4. Select **Create team**.

You become the owner of the new team. The dashboard switches to it. A new team starts with its own 14-day trial. See [plans and billing](/account/plans-and-billing).

A new team has a [default project](/account/projects#the-default-project) named **Default**, the same as the team you get when you sign up. New monitors, hosts and domains join it when you do not select a project.

### Switch teams

The dashboard shows one team at a time, the current team.

1. Select the team name at the top of the sidebar.
2. Select the team that you want to use.

**Manage teams** in the same menu opens the **Team** page.

### Team settings

Owners and managers can change the team settings under **Team → Settings**:

| Setting | What it does |
|---|---|
| **Team name** | The name in the dashboard and in emails. |
| **Contact email** | Optional. At the team's first checkout for a plan or credits, Spectate gives this address to Vatly for invoices and receipts. Without it, Spectate gives Vatly the address of the member who starts the checkout. |
| **Default timezone** | The time zone for schedules and reports. |
| **AI assistants** | Whether AI assistants can use the team through the [MCP server](/developers/mcp): **Full**, **Read only** or **Off**. |

The **Reference** section shows the **Team ID**. Support may ask for it.

## Roles

A team has five roles:

| Role | In short |
|---|---|
| Owner | Everything, including billing and deleting the team. A team has one owner. |
| Manager | Everything except billing and deleting the team. |
| Admin | Configures monitoring, alerting, incidents and status pages. Cannot change team settings, members or API tokens. |
| Member | Sees everything. Creates and changes monitors and incidents, and acknowledges and resolves alerts. |
| Billing | Billing and support only. |

## What each role can do

| What you can do | Owner | Manager | Admin | Member | Billing |
|---|---|---|---|---|---|
| See monitors, hosts, domains, alerts, incidents, status pages, projects and members | Yes | Yes | Yes | Yes | No |
| Create, change, pause and resume monitors | Yes | Yes | Yes | Yes | No |
| Delete monitors | Yes | Yes | Yes | No | No |
| Add, change and delete hosts and their metric conditions | Yes | Yes | Yes | No | No |
| Add, change and delete domains | Yes | Yes | Yes | No | No |
| Acknowledge and resolve alerts | Yes | Yes | Yes | Yes | No |
| Delete resolved alerts | Yes | Yes | Yes | No | No |
| Manage channels, escalation paths, alert sources and on-call schedules | Yes | Yes | Yes | No | No |
| Declare, update and resolve incidents | Yes | Yes | Yes | Yes | No |
| Delete incidents | Yes | Yes | Yes | No | No |
| Create, change and delete status pages, their incidents and maintenance | Yes | Yes | Yes | No | No |
| Create, change and delete projects | Yes | Yes | Yes | No | No |
| Change team settings | Yes | Yes | No | No | No |
| Invite members, change roles and remove members | Yes | Yes | No | No | No |
| Create and revoke team API tokens | Yes | Yes | No | No | No |
| Choose a plan, buy credits, see invoices | Yes | No | No | No | Yes |
| Delete the team, or restore it during the grace period | Yes | No | No | No | No |
| Transfer ownership to another member | Yes | No | No | No | No |
| Open and read support tickets | Yes | Yes | Yes | Yes | Yes |

The [public API](/developers/api) and the [MCP server](/developers/mcp) check the same permissions. A [team API token](/developers/api-tokens) can only get the abilities that the role of its creator has.

## Change a role

Owners and managers can change the role of a member. See [members](/account/members#change-a-role). A role change cannot make a member the owner or change the owner's role.

## Transfer ownership

The owner can make another member of the team the owner. The owner confirms with their password. The new owner gets the owner role, and the previous owner becomes a manager. Both get an email. A team always has exactly one owner. See [transfer ownership](/account/members#transfer-ownership) for the steps.

## Related

- [Members](/account/members): invite people, change roles, remove members and transfer ownership.
- [Plans and billing](/account/plans-and-billing): the member limit of each plan.