Team Collaboration
Team workspaces let people and agents use the same long-term memory within a project. Every atlas and memory belongs to one workspace, and the active workspace controls the dashboard scope.
Create and Switch
Open Teams from the dashboard sidebar to request Team workspace quota. Enter the number of independent Team workspaces needed and a short purpose statement. A TokST system administrator reviews the quota request. Approval adds available Team workspace capacity to the account; it does not create a workspace automatically. The request list retains pending, approved, rejected, and cancelled results.
The Owned teams section shows total, used, and available workspace quota. Select Create Team workspace whenever quota is available. Creation assigns the requester as Owner and Billing Owner, then starts an independent Team subscription. Select the Team workspace from the dashboard workspace switcher for its memories and Atlases. The global Teams page lists every Team the user owns or manages, independent of the currently selected workspace.
Team management
Each Team workspace has an independent subscription, shared calls, storage, seats, and Atlas limit. The Teams page groups Owned teams and Managed teams so one account can manage multiple product, engineering, or client Teams from one place. Every Team row shows shared usage, active and archived memories, Atlas count, active Agent count, and its latest audit activity. Owners can open the complete audit record in the Team center. Owners manage billing and plan changes; Admins manage members, invitations, roles, and collaboration from the target Workspace page. Members can create and manage their own memories under the workspace permission rules.
Roles
| Role | Workspace and members | Memories and atlases |
|---|---|---|
| Owner | Edits the workspace, invites members and admins, changes roles, removes members, and transfers ownership | Creates, edits, archives, restores, and deletes all workspace content |
| Admin | Invites and removes members; manages ordinary members | Creates, edits, archives, restores, and deletes all workspace content |
| Member | Can leave the workspace | Creates content and manages only content they own |
Each atlas inherits its workspace access rules. TokST does not use separate atlas roles in this release.
Invite Members
Open the current workspace's management page. In Pending invitations, enter one or more email addresses separated by commas or new lines, select a role, and choose an expiry period of 1 day, 1 week, or 1 month.
TokST creates one invitation for each email address. The pending list shows the recipient, assigned role, expiry date, and controls to copy or revoke an invitation link. A pending invitation grants no workspace access.
Accept or Decline
Signed-in recipients see their pending invitations at the top of Workspace management. Selecting Accept adds the recipient to the workspace with the assigned role. Selecting Decline closes the invitation. Expired, declined, revoked, and accepted invitations no longer grant access.
Ownership and Departure
An owner can transfer ownership to another member after confirmation. The previous owner becomes an admin. Owners remain in the workspace until ownership has moved to someone else.
Members and admins can leave a workspace. Owners and admins can remove eligible members after confirmation. Removing a member ends their access to shared memories, atlases, and files in that workspace.
Agent Inbox
Open Agents in the dashboard while the target workspace is selected. It contains the workspace-scoped list of trusted agt_... identities and its persistent message inbox. Members and Agents can send handoffs; Owner and Admin can view and manage all authorized workspace messages. Direct messages remain visible to their sender, recipients, and Owner/Admin. Broadcast messages fan out to active Agents in that workspace and are visible to workspace members.
The page has Agent management and Communication sheets. Management shows each stable identity, source-based nickname, API Key state, and activity time; Owner and Admin can correct a nickname for an earlier identity without an associated source record. Communication separates group broadcasts from direct messages and records the sender and recipients on every entry.
Recommended Workflow
- Create one team workspace for each product or client.
- Create atlases for durable domains such as architecture, contracts, operations, or product decisions.
- Invite people and agents with the smallest role that supports their work.
- Keep sensitive project facts in the appropriate workspace so switching workspaces keeps context isolated.