> ## 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. # Overview > Group people and their assistants — and give them a shared brain An organization rarely works as one undifferentiated blob. Sales runs differently from engineering; the finance team's data is not the marketing team's business. **Teams** bring that structure to your assistants: a team groups **people and assistants** within your organization, and gives them a **shared memory pool** — knowledge, playbooks, skills, tasks, data, and credentials that every member can use, and nobody outside can. ## Why teams exist Without teams, every assistant learns alone. Each one builds its own [knowledge, guidance, and skills](/learning/overview) from scratch, based only on the person it works with — perfect privacy, zero reuse. Teams unlock the middle ground that real organizations need: * **Learn once, share within the unit.** When one assistant on the team masters the expense process or the team's reporting SOP, every teammate's assistant can use that playbook — no re-teaching. * **Boundaries stay intact.** Shared material is visible to the team's *current members only*. Division-specific data, sensitive procedures, and elevated-access credentials stay inside the unit rather than spilling across the whole org. * **The default is still private.** Assistants keep personal memory as their [privacy floor](/teams/shared-context) — they share into a team pool only when content clearly belongs to that team, and ask when unsure. This shared-context machinery is the **most important thing teams do** — covered in depth in [Shared context](/teams/shared-context). ## Who's in a team Two kinds of members, with different rules: * **People** — colleagues from your organization, added by an org admin. * **Assistants** — in two flavors: * **Everyone's T-W1N follows its person.** Your digital twin is [private to you](/teams/membership) — hidden from everyone else in the org — and it automatically joins and leaves teams *with you*, so it always has exactly your team access, never more. * **Regular assistants join directly.** Publicly visible teammates (the ones anyone in the org can find and message) are added to teams in their own right — their access comes from their team memberships, not from whoever hired them. Details and edge cases in [People & assistants](/teams/membership). ## Where you see teams In the **Assistants** sidebar, colleagues are grouped under the teams they belong to — your T-W1N pinned at the top, team groups below, and independent colleagues listed outside any group. An assistant serving several teams shows a badge with all of them. Team administration lives under **Organizations → Teams** — see [Managing teams](/teams/managing). ## One org-wide team, if you want it For small organizations that just want everything shared, there's a shortcut: **org-wide sharing** creates a managed team called **Org** that automatically includes every current and future member and assistant. It's a blunt instrument by design — most organizations outgrow it and move to dedicated teams for the control they offer. Both are covered in [Managing teams](/teams/managing). ## What's in this section How membership works — T-W1N inheritance, public assistants, joining and leaving. The heart of teams: personal vs. team memory across knowledge, guidance, skills, tasks, data, and credentials. Creating teams, membership admin, and org-wide sharing.