> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/control-center/admin/teams.md). # Teams Teams group account members, scope them to spaces, and grant them access to specific agents and apps. They also route [Human Review](/control-center/evals/human-review.md) assignments. Open **Admin → Teams**.

The Teams list, with a Search teams field, a Create Team button, and columns for Team, Spaces, Resource Access, Members, and Actions; the Support team shows Control Center, Console and 1 agent, and Lending Ops shows Console and 2 agents — The Teams list. Resource Access counts the agents and apps each team can access.

Each team shows its **Team** name, **Spaces**, **Resource Access** (how many agents and apps it can access, for example *2 agents*), **Members** count, and an **Actions** menu. Use **Search teams** to find a team. The **Actions** menu has two options: * **Edit** — open the team to change its members and data permissions. See [Manage an existing team](#manage-an-existing-team). * **Delete** — delete the team.

A team row's Actions menu open, showing Edit and Delete — Each team's Actions menu.

A team's members can access the agents and apps in its **Data Permissions**. What each person can do with them still comes from their account-wide [roles](/control-center/admin/roles.md). ### Manage an existing team Select a team's row, or select **Edit** from its **Actions** menu, to open it. The dialog is titled with the team's name and has two sections.

The Lending Ops team dialog, with a Members table (Name, Role, Status, Action) above a Data Permissions table (Module, Name, Action), and a Save & close button at the bottom — A team's dialog: Members above, Data Permissions below. Changes apply when you select **Save & close**.

Changes you make here apply to the team only when you select **Save & close**. #### Members The Members table lists everyone on the team, with their **team role** (**Admin** or **Member**), **Status** (**Active** or **Invited**), and a delete action. To change someone's team role, open the **Role** dropdown in their row and select **Member** or **Admin**.

The Role dropdown open in a member's row, with Member checked and Admin as the other option — Change a member's team role from the **Role** dropdown.

{% hint style="info" %} A member's team role (Admin/Member) is separate from their account-wide [roles](/control-center/admin/roles.md) (Developer, Account Admin, and so on). The team role only affects what they can do within this team; their account roles still govern everything else. {% endhint %} Select **+ Add Member** to open the list of everyone on the account. Each row shows the person's name, email, and current account role. Select the **+** next to a person to add them.

The Add Member dropdown, listing existing account members with their name, email, and account role, plus an Invite New User option at the top — Add an existing account member, or select **Invite New User** to bring in someone new.

To bring in someone who isn't on the account yet, select **Invite New User** at the top of the list. This opens a form for their **First Name**, **Last Name**, **Email**, and the account-wide [roles](/control-center/admin/roles.md) they'll hold once they accept. They're added to this team automatically when they join. #### Data Permissions The Data Permissions table lists the apps and agents the team can access, by **Module** (for example **Agent**) and **Name**, with a delete action. Select **+ Add Permission** to search the account's agents and apps and select the **+** next to any you want to add.

The Add Permission dropdown open above the Data Permissions table, offering the Knowledge Base Resolver agent with a + action; two agents are already listed — Search the account's agents and apps and add the ones this team needs.

### Create a team Select **+ Create Team**. The dialog has two steps. {% stepper %} {% step %} ### Set up the team * **Team name** — a label, such as *Lending Ops*. * **Spaces** — which products this team can operate in: select **Console**, **Control Center**, or both. This is separate from the agent and app permissions you set in step 2. * **Members** — search the account's people and check the ones to add. The count of people selected shows beside the heading. You can change members and their team roles later. Select **Invite someone new** to invite a person who isn't on the account yet. Select **Continue**. {% endstep %} {% step %} ### Set agent and app permissions Choose what the team can access, in two lists: * **Agent permissions** — the specific agents to grant this team access to. * **App permissions** — the specific apps to grant this team access to. Each list has a search field, a count such as *0 of 3 selected*, and **Select all** and **Clear**. Select **Create Team** to finish, or **Back** to return to step 1. {% endstep %} {% endstepper %}

Create Team step 1 of 2, with the Team name field set to Lending Ops, Console and Control Center buttons for Spaces with Console selected, a Members search showing 1 selected, and an Invite someone new link — Step 1: name the team, pick its spaces, and choose its members.

Create Team step 2 of 2, with an Agent permissions list of three agents (0 of 3 selected) and an App permissions list, each with search, Select all and Clear, and Back, Cancel and Create Team buttons — Step 2: grant the team access to specific agents and apps.

{% hint style="info" %} Complete both steps. The team's agent and app selections aren't saved until you select **Create Team** in the second step. {% endhint %} #### Invite someone new Selecting **Invite someone new** in step 1 opens **Invite New User**. The person is invited to the account and added to this team once the team is created. Every field is required. * **First Name** and **Last Name**. * **Email** — the address they'll sign in with. See [How invited people sign in](/control-center/admin/users.md#how-invited-people-sign-in). * **Role** — one or more account-wide [roles](/control-center/admin/roles.md), such as **Viewer** and **Approver**. * **Team Role** — **Member** or **Admin** within this team.

The Invite New User form with First Name, Last Name and Email filled, and the Role dropdown open listing Viewer, Billing Manager, Approver, Developer, Governance Manager, Auditor, Account Admin, and Organisation Admin, with Viewer and Approver checked — Select one or more account roles for the person you invite.

The Invite New User form with Viewer and Approver selected as roles and the Team Role dropdown open, showing Member checked and Admin — Set their team role as well as their account roles.

--- # 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.uptiq.ai/control-center/admin/teams.md?ask=&goal= ``` `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.