Workspaces
A Workspace is a top-level container for atlases. Workspaces provide organizational boundaries — you can have a personal workspace, a team workspace, and separate workspaces for different clients or projects.
Concept
| Property | Description |
|---|---|
| Name | Human-readable label (e.g., "Personal", "Engineering Team") |
| Type | Personal (single-user) or Team (multi-user) |
| Atlases | All atlases within this workspace |
| Members | Users with access (team workspaces only) |
Create and manage Workspaces in the Dashboard. Authorized Agents use the Cloud MCP Workspace tools.
Default Workspace
When you sign up, TokST creates a default workspace named "Personal" (or your account name). This is your active workspace until you create or switch to another.
Create a Personal Workspace
Create a personal Workspace from the Dashboard. Its Workspace limit follows your personal plan.
Team Workspaces
A Team workspace is provisioned together with its Team subscription. Team members join through an invitation and use the Team workspace's shared seats, calls, storage, and Atlas limit. Workspace type remains fixed after provisioning.
List Workspaces
The Dashboard lists every Workspace you can access and marks the active Workspace. Pending team invitations appear in the same governed interface.
Switch Workspace
Switching Workspaces changes the available Atlases. The Dashboard and Cloud MCP both apply the authenticated Workspace scope. Accept a pending invitation before using its Team Workspace.
Agent Collaboration
Open Agents to manage Runtime devices and Agent bindings for the current Workspace. Only Agents explicitly created from available adapters become executable contacts. Cloud MCP clients retain separate audit identities for memory operations.
Open Communication for long-lived direct chats and Agent groups. Open Tasks for explicitly assigned work. Open Sessions for opt-in automatic capture. Each surface follows the selected Workspace and keeps its own lifecycle.
Archive a Workspace
Workspace archival is available through the REST API and remote MCP server:
curl -X DELETE https://api.tokst.com/v1/workspaces/<workspace-id> \
-H "Authorization: Bearer $TOKST_API_KEY"
Remote MCP clients can call tokst_workspace_archive with workspaceId and confirm: true. Archiving preserves the workspace, its knowledge bases, files, and audit history. Permanent removal is available only from the Dashboard archive view.
Personal vs. Team Workspaces
| Aspect | Personal | Team |
|---|---|---|
| Members | Single user | Multiple users |
| Atlases | User-created | Shared among members |
| Visibility | Private to you | Visible to all members |
| Use case | Personal notes, experiments | Project knowledge, team docs |
Team workspaces use role-based access. Read the Team Collaboration guide before inviting members.
Best Practices
- Use workspaces for separation — Personal experiments belong in a personal workspace, team knowledge in a team workspace
- Name workspaces clearly — "Personal", "Team Engineering", "Client A" are self-explanatory
- One team workspace per team — Don't create overlapping workspaces for the same group