Skip to main content
Teams contain people and assistants, and the platform treats the kinds of assistants — your private T-W1N, personally-supervised hires, and team assistants — very differently. Getting these distinctions right is most of understanding teams.

​
Your T-W1N: private, and it follows you

Everyone in an organization has their own T-W1N — their digital twin. Two rules define how it relates to teams:
  1. It’s hidden from everyone else. Your T-W1N doesn’t appear in colleagues’ assistant lists, can’t be messaged by them, and can’t even be opened by an org admin. It works for you and answers to you, full stop.
  2. It inherits your team access — exactly. When you’re added to a team, your T-W1N automatically becomes a member too; when you leave, it leaves with you. You never manage its memberships, and it can never have access you don’t have.
The result: your twin can read and contribute to the shared pools of every team you’re on — the sales team’s playbooks, the ops team’s data — while remaining completely invisible to your colleagues. They benefit from what it shares into team pools without ever interacting with it directly.

​
Hired assistants: visible, and members in their own right

Hired assistants are the opposite on both counts:
  1. They’re visible across the organization. Colleagues (with the appropriate org permissions) can find them in the assistant list, open their profiles, and message them — they’re shared team members in the fullest sense.
  2. Their team memberships are their own — granted explicitly, not inherited from any person. One assistant can serve several teams at once (the sidebar shows a badge listing all of them).
Within that, two ownership models:
  • Team assistants — owned by a team rather than a person. Hiring defaults to this: you pick an owning team during the hire, the team becomes the assistant’s home, and membership in that team is structural — it can’t be removed from its owning team, and the team can’t be deleted while it owns assistants. Everything about them is covered in Team assistants.
  • Personally-supervised assistants — owned by the person who hired them (choose Personal during the hire). They keep a private memory as their privacy floor and join teams as an add-on: each membership layers that team’s shared pool on top.
This is what makes hired assistants useful as specialists: a repairs coordinator serving the whole repairs team, a reporting assistant embedded in finance. They belong to the unit, not to a person. For how these teammates come to exist — and how their identity differs from a T-W1N’s — see Hiring.

​
Joining and leaving

Membership is live — access tracks it immediately:
  • Joining a team gives a member (human or assistant) access to the team’s whole shared pool — knowledge, guidance, skills, tasks, data, credentials — from that moment. It also puts them in the team’s group chat.
  • Leaving (or being removed) ends that access just as cleanly. The shared content itself stays with the team for the remaining members — people take their access away with them, not the team’s accumulated know-how.
  • The one structural exception: a team assistant cannot leave or be removed from its owning team — that team’s pool is its entire memory. It can join and leave any other team freely, like any assistant.
  • Leaving the organization removes a person from all its teams — and their T-W1N from all of them too, automatically.
Running assistants are told when their team access changes, so a revocation doesn’t wait for the next session.

​
Who’s who at a glance