---
title: "Teams"
description: "How teams group principals so roles can be assigned once and shared."
canonical: "https://docs.cm.com/governance/guides/core-concepts/teams"
---

# Teams

> How teams group principals so roles can be assigned once and shared.

Source: https://docs.cm.com/governance/guides/core-concepts/teams

A **team** is a group of users. Give a role to the team once, and every member gets it.

## Why use a team

- **Less work.** Assign a role to "Support" instead of to each person.
- **Easy changes.** Add someone to the team to give them access. Remove them to take it away.

## How teams work

- Teams belong to an organization and are created in the Governance portal.
- A team can receive role assignments, like a user.
- A member gets all the access the team is given, on top of any access they have directly.
- When a member is removed from a team, they lose the access they got through it. Access given to them directly stays.

## Example

An organization creates a team called **Integration Specialists** and assigns it a role that allows configuring agents. Anyone added to the team can configure agents. When a specialist leaves the team, they can't.

## Related

- [Principals](https://docs.cm.com/governance/guides/core-concepts/principals)
- [Role assignments](https://docs.cm.com/governance/guides/core-concepts/role-assignments)
- [Roles](https://docs.cm.com/governance/guides/core-concepts/roles)