---
title: Team management
description: Create and switch Teams, manage member roles, and control which App
  connections members can use.
lang: en
canonical_url: https://oomol.com/en/docs/team-management/
markdown_url: https://oomol.com/en/docs/team-management.md
---

# Team management

A Team is the internal collaboration boundary in OOMOL Connector. Team members can use authorized Apps in the same Team without receiving raw provider tokens.

Use a Team for coworkers, collaborators, and internal Agents. If you are building a SaaS product and need to isolate end users, use [Connector for SaaS](/en/docs/saas/).

## What a Team manages

A Team can contain:

- Members and their roles.
- Apps connected in that Team.
- The App connections each member may use.
- CLI, MCP, and SDK calls scoped to that Team.

Switching Teams changes the visible connections, configuration, and call scope. Confirm the selected Team before running a task.

## Member roles

| Role | Primary purpose |
| --- | --- |
| Creator | Creates and manages the Team, has default connection access, and cannot be removed |
| Admin | Helps manage members, roles, and connection access |
| Member | Uses the App connections granted by an administrator |

Available operations can also depend on the current plan, seat count, and member status.

## Seats and billing

The Team plan is billed per seat. Before adding members or expanding Team usage, open [Billing in Console](https://console.oomol.com/billing) to review the current plan, seats, and charges. The billing page is the source of truth for current pricing.

## Configure a Team

In the Team management page in Console:

1. Create a Team or switch to an existing one.
2. Add members and assign member or admin roles.
3. Connect the Apps that the Team needs to share.
4. Grant members access to the permitted connections.
5. Disable a member or revoke access when it should be paused.

[Manage Teams in OOMOL Console →](https://console.oomol.com/members)

## Select a Team for an Agent

The Console installation page includes a Team selector and writes the selected Team into the generated configuration:

- oo CLI login uses `--team=<team-name>`.
- MCP configuration uses the `x-oo-team-name` header.

This keeps the Agent environment scoped to an explicit Team even if the default Team changes later. Return to the [Quickstart](/en/docs/agents/) to choose another Team in Console.

Continue with [Access control](/en/docs/access-control/) for personal OAuth scopes, Team member connection access, and the corresponding Console entry points.