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

# Virtual Teams

> Split your organization into sub-teams, each with isolated members, dedicated workspaces, and its own credit pool

## Overview

Virtual Teams lets you divide your Qwairy organization into independent sub-teams. Each sub-team has its own members, workspaces (brands), and credit balance — all allocated from the parent organization's pool.

**Available on Business and Enterprise plans.**

Common use cases:

* Agencies managing separate client accounts under one billing entity
* Multi-brand groups isolating each business unit (e.g. different divisions, regional entities)
* Internal teams with separate monitoring budgets

***

## Concepts

| Term                | Description                                                                                                                          |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Organization**    | Your main Qwairy account (the parent). Owns the global credit pool and workspace quota.                                              |
| **Sub-team**        | An isolated workspace created under your organization. Has its own members, brands, and credit balance.                              |
| **Credit pool**     | Credits held at the organization level, not yet allocated to any sub-team.                                                           |
| **Workspace quota** | The number of brands (workspaces) available across your plan, shared between the organization's own brands and sub-team allocations. |

***

## Managing Sub-Teams

Go to **Team Management > Virtual Teams** — `https://www.qwairy.co/dashboard/team/virtual-teams`

The page shows:

* The organization's remaining credit pool and workspace quota
* A breakdown bar showing how credits are distributed across sub-teams
* The list of all sub-teams with their balance, usage, and workspace count

***

## Create a Sub-Team

1. Click **Create** in the top-right of the Sub-teams table (or in the empty state if no sub-teams exist yet)
2. Fill in the form:
   * **Name** — identifies the sub-team in the switcher and admin views
   * **Credits to allocate** — optional; use the 25% / 50% / Max presets or enter a custom amount. Can be adjusted later.
   * **Workspace quota** — number of brands this sub-team can create (minimum 1)
3. The preview section shows the impact on your organization's credit pool and quota before you confirm
4. Click **Create sub-team**

The sub-team is immediately available in the team switcher. You are automatically set as its Owner.

<Note>
  Workspace quota cannot exceed the available quota in your organization pool. Credits and quota can both be adjusted after creation.
</Note>

***

## Allocating and Reclaiming Credits

Credits flow **from the organization pool to sub-teams**, and back.

### Allocate credits

1. In the Sub-teams table, click **Allocate** next to the target sub-team
2. Enter the amount to transfer (use the 25% / 50% / Max presets or enter a value)
3. The preview shows balances before and after
4. Confirm — the transfer is immediate and recorded in the credit ledger

### Reclaim credits

Same dialog — switch to **Reclaim** mode and enter the amount to pull back into the organization pool. The sub-team must have enough available credits.

<Note>
  Credit transfers appear in usage analytics as **adjustments**, not as consumption. They do not affect burn rate or projections.
</Note>

***

## Adjusting Workspace Quota

To change a sub-team's workspace quota after creation:

1. Click **Quota** next to the sub-team
2. Enter the new quota value
3. Confirm

Constraints:

* The quota cannot be reduced below the sub-team's current number of active brands
* The total quota allocated across all sub-teams plus the organization's own active brands cannot exceed the plan's workspace limit

***

## Transfer a Workspace into a Sub-Team

Once you have at least one sub-team, you can move a live workspace (brand) between the parent organization and any sub-team, or between sub-teams. The workspace carries its complete history with it, and the move never costs you extra workspace quota.

**Available on Business and Enterprise plans.** Only Owners and Managers of the parent organization can move workspaces, and transfers are always managed from the parent organization account.

### What Moves with the Workspace

* **Full monitoring history**: every past answer, prompt, competitor, source, and analytics figure travels with the workspace. Nothing is lost or reset.
* **Access**: members of the destination team gain access to the workspace and all of its history. Parent-organization members below Manager who previously saw it lose access once it moves into a sub-team.
* **Share links**: existing public share links for the workspace keep working under the new team.
* **Workspace group placement**: the workspace's place in any workspace group is cleared, since groups belong to a specific team.

### Move an Existing Workspace

1. Go to **Team Management > Virtual Teams** from your organization account: `https://www.qwairy.co/dashboard/team/virtual-teams`
2. Make sure you have at least one sub-team. If none exist yet, create one first with **Create**.
3. Click **Move workspace** at the top of the page. This button appears once you have one or more sub-teams.
4. In the **Workspace to move** dropdown, pick the live workspace you want to relocate. Each option shows the workspace name and the team it currently belongs to.
5. In the **Move to** dropdown, choose the destination: another sub-team, or your organization itself (listed with an **(organization)** tag next to its name) to bring a workspace back to the parent. The workspace's current team is not offered as a destination.
6. Review the confirmation summary. It shows the move as **current team -> destination** and explains what changes (history carried over, who gains and loses access, share links continue to work).
7. Click **Move workspace** to confirm. A toast confirms the workspace was moved, and it appears under the destination team.

You can also move workspaces at creation time: in the **Create** dialog for a new sub-team, tick one or more workspaces under **Move existing workspaces** to move them into the new sub-team the moment it is created.

### Quota and Credits

A workspace carries its reserved workspace slot with it. When it leaves a team that team's quota goes down by one, and when it enters a team that team's quota goes up by one, so your organization's total workspace allowance never changes.

* Because every transfer is net-zero on your overall allowance, a move is never blocked for lack of quota, and bringing a workspace back to the parent organization always succeeds.
* You can create a new sub-team purely by moving existing workspaces into it, even with no free workspace quota left, since those workspaces bring their slots along. The new sub-team's quota must be at least the number of workspaces you move into it.

<Note>
  If the destination sub-team has no credits, monitoring for that workspace pauses until you allocate credits to the sub-team. The workspace's future monitoring spend draws from the destination team's credit balance.
</Note>

### After the Move

The workspace is available in the destination sub-team immediately, and its members can open it right away. Its analytics and reporting finish moving over shortly after, so for a brief period some figures may look momentarily inconsistent before everything settles. When the destination is a sub-team, it shows a small **migrating** indicator next to its name while the move settles, which clears on its own once the move is complete.

Transfers are reversible and repeatable: you can bring a workspace back to the parent organization or move it on to another sub-team at any time. Only one transfer per workspace runs at a time. If a workspace is still settling from a previous move, a new move for it is declined until that finishes.

### Constraints

* Only live, standard workspaces can be moved. Draft and audit workspaces are not eligible.
* The destination must be the parent organization or one of its active sub-teams. You cannot move a workspace to the team it is already in.
* Members below Manager cannot move workspaces, and sub-team members do not initiate transfers themselves.

### Give a Client Scoped Access to One Brand

Transferring a workspace into a dedicated sub-team is how you give a client (or an office, business unit, or brand pod) full, hands-on access to a single brand without exposing the rest of your organization.

1. Create a sub-team for that client with its own members.
2. Move the relevant workspace into it, either at creation time via **Move existing workspaces** or afterwards via **Move workspace**.

The client's sub-team members see and manage only the workspaces in their sub-team, with their own credit pool and workspace quota, and never see the rest of the organization. The full history of the workspace comes along, so the client gets continuity from day one, while parent members below Manager lose direct visibility into that brand.

Use a transfer (rather than the [Viewer](/documentation/workspace/viewers) role) when the client needs to actively manage the brand, not just read it. Viewer access stays read-only and brand-scoped within your organization, while a sub-team transfer gives full management in an isolated team.

***

## Members in Sub-Teams

Each sub-team has its own isolated member list. Members of sub-team A cannot see sub-team B's workspaces or data.

To invite members to a sub-team, switch to that sub-team in the team switcher, then go to **Team Management > Members**.

**Owners and Managers of the parent organization automatically have access to all sub-teams** without needing a separate invitation.

### Roles

Sub-teams use the same role hierarchy as the main organization: Owner, Manager, Member, Viewer. See [Manage Members](/documentation/team/manage-members) for details.

***

## Billing and Plan

Sub-teams do not have their own subscription. They inherit the plan of the parent organization — this determines which features (AI models, export, integrations) are available within the sub-team.

Billing is managed exclusively at the organization level. Sub-team members do not have access to the Billing tab.

***

## Related

* [Credits](/documentation/get-started/credits) — How credits are consumed
* [Manage Members](/documentation/team/manage-members) — Invite and manage team members
* [Billing](/documentation/team/billing) — Manage your subscription