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

# Managing teams

> Creating teams, membership admin, and org-wide sharing

Team administration lives under **Organizations → Teams** in the Console,
alongside Members and Roles. Creating and changing teams requires org admin
permissions (Owner or Admin role).

## Creating and editing teams

* **Create new team** — give it a name and an optional description, and
  you're done. You're added as the first member automatically — and so is
  your T-W1N, so the team's shared pool is usable immediately.
* **Write the description well.** It's more than a label: assistants read
  team descriptions when [deciding where content
  belongs](/teams/shared-context), so "Repairs — work orders, contractor
  coordination, and tenant communication for the housing patch" routes far
  better than "Team 2".
* **Update or delete** from the team's row menu. Deleting a team is
  consequential: it permanently removes the team's entire shared pool —
  the knowledge, playbooks, tasks, and data accumulated in it.

## Managing members

From each team's menu:

* **Add member / Remove member** — org members join and leave the team.
  Each person's T-W1N [follows them in and out](/teams/membership)
  automatically.
* **Assistant members** — specialist assistants are added to teams in
  their own right. The simplest way is to ask your org's T-W1N —
  org-shaped setup like team creation, membership, and shared credentials
  is exactly the work it's for.

Access changes take effect immediately, including for assistants that are
mid-session.

## Org-wide sharing: the one-team shortcut

When you create an organization (and any time after, from the Teams tab),
you choose a data-sharing posture. The Console explains the trade
directly:

> By default, all skills acquired and knowledge retained are personal to
> each user's own private teammate… Each user's teammate learns in
> isolation, based on that user alone. If you'd like the teammates to also
> have the option to read/write from a shared pool across the org where
> appropriate, select shared below.
>
> If you want more granular control, then it is best to set up dedicated
> teams. Users and teammates can then be assigned to teams to enable
> controlled sharing within specific teams, rather than blanket org-wide
> sharing.

Enabling **org-wide sharing** creates a managed team named **Org** that
automatically includes every current and future member and assistant.
A few things to know about it:

* **It's managed.** The Org team can't be renamed, edited, or deleted by
  hand — it exists exactly as long as org-wide sharing is on.
* **It's still selective.** Even in shared mode, assistants decide what's
  genuinely useful to share versus personal — and **transcripts, emails,
  and files are never shared** through the org pool. Only knowledge,
  skills, and general know-how flow into it, creating what the Console
  calls "a faster hive-mind approach to learning across the team."
* **Turning it off deletes the pool.** Disabling org-wide sharing removes
  the Org team *and all shared content in it* — the Console warns you, and
  it cannot be undone.

## Choosing your structure

| Setup                      | Fits                                                                                         |
| -------------------------- | -------------------------------------------------------------------------------------------- |
| **No teams** (all private) | Solo users; orgs where assistants genuinely shouldn't share                                  |
| **Org-wide sharing only**  | Small orgs where everyone works on everything                                                |
| **Dedicated teams**        | Any org with units, divisions, or sensitivity boundaries — the recommended shape as you grow |

The options combine: you can run org-wide sharing for general know-how
*and* dedicated teams for division-specific or sensitive material — the
narrower pool keeps its boundary regardless.