The workspace account
T-W1N connects to your account. That’s the point of a twin: it reads your inbox, checks your calendar, works in your Drive, and anything it sends from your workspace shows up as you. It borrows your access — and is therefore bounded by it. A hired teammate gets a brand-new account of its own. The hire flow is explicit about this:Create a new Google or Microsoft account for , so they can join your team, gain their own unique access controls to the files and applications you use via their own new account, and can work alongside your team. Do not connect to your own Google/Microsoft account. Only T-W1N should have access to your personal account.This is where hired teammates earn their dedicated accounts:
- Gated access, managed like any employee’s. Your IT team shares exactly the drives, folders, and apps the teammate’s role needs — no more. Its permissions are its own, auditable, and adjustable without touching anyone’s personal account.
- A real presence in your org’s tools. With its own Microsoft 365 or Google identity, the teammate appears in Teams and Slack as itself — a named profile colleagues can DM, @mention, and add to channels — rather than as an extension of any one person.
- Its own mailbox and calendar. Mail to the teammate lands in its inbox; meetings it schedules come from its calendar; threads it runs belong to it, and survive any individual employee’s departure.
Contact details
T-W1N’s contact details are platform-managed — there’s nothing to configure. Its email, phone, and WhatsApp run on shared platform pools: when you message one, the platform recognizes your verified identity and routes the conversation to your twin. The same address serves everyone’s twin — a routing layer, not a personal identity. A hired teammate gets its own numbers and addresses, provisioned in Contact Details: a dedicated phone number for calls and SMS, its own WhatsApp, its connected mailbox. When a client calls the repairs teammate’s number, they reach the repairs teammate — whoever they are and whether or not they’re on the platform at all.Integrations
The same logic extends to connected apps:- T-W1N’s integrations naturally center on your accounts — its purpose is acting on your behalf inside your tools.
- A hired teammate’s integrations should be connected through its own dedicated workspace account wherever possible — the CRM seat, the ticketing login, the OAuth grants all belonging to the teammate itself. Its credential vault is its own, and access reviews treat it like any other member of staff.
Visibility and lifecycle
| T-W1N | Hired teammate | |
|---|---|---|
| Created | Automatically, for every person | Deliberately, via Onboard |
| Visible to colleagues | Never — private to you | Yes — listed, searchable, messageable |
| Talks to | You only | Anyone, governed by response policies |
| Name & look | Fixed | Your choice — name, persona, avatar, voice |
| Workspace account | Yours | Its own, newly created |
| Contact details | Platform-managed pools | Its own dedicated channels |
| Team access | Mirrors yours | Its own memberships |
| Can be let go | No | Yes — End contract |
Same brain, different passport
It’s worth repeating what doesn’t differ: capability. The hire form says it plainly —The bio doesn’t influence the teammate’s abilities. All teammates come with the same foundational skills and can specialize in whichever area you want them to.Every teammate learns, schedules, browses, and builds the same way. Choose between twin and hire based on identity and audience — who it acts as, and who it serves — not on what it can do.