Team
Team keeps the people and shared work around your organization in one place. Find directory-verified coworkers, send Broadcasts and Asks, approve incoming memories, maintain a separate team memory, and manage the phones and computers that belong to you.
Private work does not become team work by accident. Connections require consent, incoming memories wait for your approval, and team communication travels through encrypted channels tied to verified organization identities. Your personal memory remains separate.
⧉ Verified people
Discover coworkers through your organization and approve connections deliberately.
⧉ Broadcasts & Asks
Send a directive or question, then follow acceptance and responses.
⧉ Shared context
Accept or discard incoming memories and keep curated notes in team memory.
⧉ Your devices
Pair hardware you own and choose which devices receive full memory sync.
/team, or choose Team from Studios. Type /pair to go directly to Team → Devices.What it is#
Team is the studio for organization membership, direct trust relationships, team-directed communication, shared context and cross-device sync. Its six tabs keep distinct jobs separate: people and consent, directives, questions, incoming handoffs, curated team notes, and devices. Signals is intentionally a separate Studio for scanning organization-wide outcomes.
People & identity#
Sign in with Zimac and turn on sharing to appear in your organization's directory. Coworkers in the same organization appear automatically with their directory-attested identity; no pairing code is needed just to find them. A direct connection still requires a request and an explicit accept. Once connected, you can compare the safety code on both devices for extra assurance and disconnect at any time.
The six tabs#
Each tab has one clear responsibility:
Broadcasts and Asks have their own guides because they have different response contracts. A Broadcast asks teammates to accept or decline a directive; an Ask collects answers. Both are composed and reviewed inside Team.
Shared context#
The Shared tab is a consent queue. A memory sent by a connected coworker appears in your inbox first; choose Accept into memory or Discard. The same tab lists everything you have approved for connected people to pull, with a control to stop sharing each item.
Team memory is different: it is an optional, curated note space with its own search, categories and add/edit/delete controls. New notes sync to teammates you have connected, encrypted, while your personal memory stays separate. Signals do not land here automatically; they remain in the Signals feed.
Your devices#
The Devices tab is for a phone or computer you own. Create or paste a one-time invite, compare the safety code on both screens, and mark a peer as My device only when it really is yours. That choice enables full two-way memory sync, including future creates, edits and deletes. Setup inheritance — including model access — always arrives as a separate approval request. See the Team → Devices guide for the full flow.
Where Signals lives#
Signals is a standalone Studio, not a Team tab. It is the glanceable organization feed for on-track work, wins, FYIs, risks, blockers and requests for help. Team includes a shortcut to open or enable it, while Broadcasts and Asks stay in Team because they require direct action or a response.