# Teams (https://docs.fuser.studio/docs/teams/team-groups)

A team is a named slice of your workspace with its own members, folders, and visibility. Teams are useful for separating Brand from Motion, or Production from R\&D, without making every project visible to everyone.

This page covers creating a team, picking its visibility, managing membership, and archiving a team you no longer need.

## Creating a Team [#creating-a-team]

    ### Open the Teams panel [#open-the-teams-panel]

    Open **Settings** → **Workspace** → **Teams** and click **Create Team**.

    ### Set name, color, and visibility [#set-name-color-and-visibility]

    * **Name** — what the team is called.
    * **Color** — a small dot used to label the team in member rows and folders.
    * **Visibility** — who can discover and join the team (described below).

    ### Become the first Manager [#become-the-first-manager]

    The person who creates a team automatically becomes its first **Manager**.

> [!NOTE] Who can create teams?
>
> By default any workspace **Owner** or **Admin** can create teams. Whether regular **Members** can create teams depends on the **Members Can Create Teams** policy in [Workspace Settings — Sharing Policies](https://docs.fuser.studio/docs/teams/workspace-settings.md#sharing-policies).

## Team Visibility [#team-visibility]

Visibility controls who can discover the team and what non-members see of its work.

* **Open** — discoverable by every workspace member. Non-members can see the team's published content at the workspace root default access level. Members can self-join.
* **Closed** — discoverable, but joining requires an invitation from a **Manager**. Non-members can't see the team's projects.
* **Private** — invisible to non-members. Only the team's own members know it exists.

You can change visibility later from the team's row in the **Teams** panel — only the team's Managers and workspace Admins can do this.

> [!NOTE] Open does not mean public
>
> **Open** means discoverable by everyone in your workspace, not by the outside world. Nothing in your workspace is ever exposed to non-members of the workspace by default — for that, see [Sharing](https://docs.fuser.studio/docs/teams/sharing.md).

## Team Roles [#team-roles]

Inside a team, members have one of two roles:

* **Manager** — update team settings, add or remove members, change visibility, archive the team.
* **Member** — read team content according to the team's visibility rules.

You change a team member's role from the team detail view. The team's creator is its first Manager; promote others as the team grows.

Workspace **Admins** and **Owners** can manage any team without needing to be members of it.

## Adding and Removing Members [#adding-and-removing-members]

In the team's detail view, click **Add Member** to pick from the workspace's member list. Removing a member is the **Remove** button on their row. Removed members lose access to the team's folders and projects immediately, unless they have explicit shares.

For **Open** teams, members can also self-join from the workspace's team list — no manager action required.

## Archiving a Team [#archiving-a-team]

When a team's work is done but you want to keep its history, **Archive** the team instead of deleting it. The team's row stays visible (with an **Archived** badge), and its folders and projects stay intact.

While a team is archived:

* **Non-members lose access entirely.** Even **Open** teams stop granting access to outsiders.
* **Members are capped at View access.** Even on folders set to default-Edit, archived-team members can only read.
* Explicit Edit shares still work — they override the cap.

To resume work, click **Unarchive** on the team's row. To remove the team permanently, click **Delete Team** — this is irreversible and removes the team's folders and projects unless you've moved them out first.

> [!WARNING] Archiving caps editing across the team
>
> Even if a folder inside an archived team has default-Edit access, members only get View. If you need ongoing edit access while a team is archived, grant explicit shares to the people who need them — see [Sharing](https://docs.fuser.studio/docs/teams/sharing.md).

## What's Next? [#whats-next]

  - [Folders](https://docs.fuser.studio/docs/teams/folders.md): Teams own folders — set them up and choose default access.

  - [Access Reference](https://docs.fuser.studio/docs/teams/access-reference.md): Full rules for who sees what across teams, folders, and projects.