Overview

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, gives them a shared memory pool — knowledge, playbooks, skills, tasks, data, and credentials that every member can use, and nobody outside can — and a group chat where all of them, human and AI, work together in one thread.

​

Why teams exist

Without teams, every assistant learns alone. Each one builds its own knowledge, guidance, and skills 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.
• Privacy floors are respected. Personally-supervised assistants keep personal memory as their privacy floor — they share into a team pool only when content clearly belongs to that team, and ask when unsure. (Team assistants are the deliberate exception: they belong to the team, so the team pool is their memory.)
• A team can hire its own assistants. A team assistant is owned by the team itself — no single supervisor, everyone can work with it, and everything it learns is shared with the team by construction.

This shared-context machinery is the most important thing teams do — covered in depth in Shared context.

​

Who’s in a team

Three kinds of members, with different rules:

• People — colleagues from your organization, added by an org admin. Humans appear in the workspace roster with live online indicators, and you can message any of them directly.
• Everyone’s T-W1N follows its person. Your digital twin is private to you — 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.
• Hired assistants join in their own right — and come in two ownership models:
  • Team assistants (the default when hiring) are owned by a team: the team’s shared pool is their entire memory, anyone on the team can work with them, and no individual holds a supervisor position. See Team assistants.
  • Personally-supervised assistants are owned by one person but can still be added to any number of teams, layering team pools on top of their private memory.

Details and edge cases in People & assistants.

​

Where you see teams

The Assistants sidebar is a full org roster, grouped into three sections: Teams (each team with its members beneath it — an assistant serving several teams shows a badge listing them, and team-owned assistants carry a Team-owned badge under their owning team), Real (your human colleagues, with online indicators), and Virtual (assistants that aren’t in any team). Your own T-W1N stays pinned at the top. Selecting a team opens the team’s workspace:

• Chat — the team’s group chat, one thread shared by every member, human and AI. Messages behave like a conversation in any group channel: every member sees them, assistants read the room and reply when a message is genuinely for them (an @mention helps), and their replies are visible to — and can wake — their AI teammates.
• Members — the roster with online status, and a Hire for this team action to onboard a new team assistant directly into it.
• Every brain section, team-scoped — Tasks, Dashboards, Contacts, Transcripts, Knowledge, Functions, Guidance, and Data all show the team’s shared pool rather than any single assistant’s memory.

Selecting an assistant gives the complementary view: each brain pane has scope chips — All, Personal, and one per team — so you can see its private memory, any single team pool, or the exact merged picture the assistant itself works from. Team administration lives under Organizations → Teams — see Managing teams.

​

One org-wide team, on by default

New organizations start with org-wide sharing enabled: a managed team called Org that automatically includes every current and future member and assistant. It’s the simplest useful structure — one shared pool for general know-how, and the natural home for company-wide team assistants. Organizations that need boundaries add dedicated teams on top (the narrower pool always keeps its boundary), or opt out to fully private at creation. All covered in Managing teams.

​

What’s in this section