Workspaces
Workspaces organize documents, conversations, and access inside an organization. Use them for projects, teams, departments, or client-specific knowledge.
Organization-Level vs Workspace Content
Organization-level content
Use this for shared policies, templates, and documents that should be available broadly across the organization.
Workspace-specific content
Use this for focused project rooms, customer accounts, departments, or other collections with their own members and conversations.
How Workspace Context Works
Documents
Without a workspace, uploads and lists use organization-level files. With a workspace, uploads and lists target that workspace.
Conversations
Organization-level and workspace conversations are listed separately, based on the selected context.
Answers and search
Workspace questions search organization-level files plus files in that workspace. Without a workspace, search uses organization-level files only.
Workspace Memory (Project Context)
Each workspace can have durable memory — a persistent project context that helps the AI understand background knowledge specific to that workspace. Unlike documents, workspace memory is not cited as a source. It acts as background context that improves answers without appearing in citations.
What to store
Domain terminology and definitions
Client-specific details or project rules
Reusable background that applies across many conversations
Characteristics
One memory per workspace (empty by default)
Maximum 20,000 characters
Editable by workspace owners and admins
Changes are versioned with an audit trail
Two ways to update
Manual editing — Workspace owners and admins can edit memory directly from workspace settings.
Auto-extraction — The AI can automatically extract durable facts from your messages and suggest memory updates (only when you explicitly state project facts).
Metadata and Constraints
Responses include id, organization_id, name, description, created_by, timestamps, member_count, and user_role.
Names are required, must be 1–100 characters, and must be unique within an organization.
Descriptions are optional. Creating a workspace makes the creator the workspace OWNER.
Creating, Updating, and Deleting
Organization admins can create workspaces with a name and optional description.
Workspace admins, workspace owners, and organization admins can update workspace details.
Workspace admins, workspace owners, and organization admins can delete workspaces.
Deleting a workspace is destructive. Review the workspace carefully before deleting it.
Roles and Membership
Workspace roles are separate from organization roles. Users must first belong to the organization before they can be added to a workspace.
OWNER is assigned to the creator when the workspace is created.
ADMIN and MEMBER can be assigned when adding or updating workspace members.
Owner transfer is not documented for workspace membership.
Organization admins can manage and list all workspaces; regular members need explicit workspace membership.
Empty States and Troubleshooting
If you cannot see a workspace, ask an organization admin to add you as a member.
If a workspace has no documents, check whether files were uploaded while that workspace was selected.
If a conversation is missing, switch between organization-level and workspace views.
Access errors usually mean a missing organization or workspace context, a missing workspace, no membership, or insufficient admin/owner access.
Workspace memory is background context, not a document source. It improves answers silently and is never cited as a source. If memory seems ignored, check that it has been saved and that you have selected the correct workspace.