Membership and roles
Workspaces are where viewers, editors, reviewers, and admins are scoped. This keeps editing and publish authority aligned with the team actually responsible for the content.
Concepts
Workspaces are the team boundary for knowledge operations.
A workspace is the top-level container in SnippetGraph. It defines who can participate, which knowledgebases live together, how releases are governed, and where exports are delivered.
Shared Knowledgebases
Real-time network sync active
Synced
Safety-Guardrailsv2.0
SnippetGraph Master Source
Support Agent
Greeting Protocol
Safety-Guardrailsv2.0
Refund Policy
Sales Copilot
Safety-Guardrailsv2.0
Enterprise Pricing
Competitor Intel
Internal HR
Remote Work FAQ
Benefits Wiki
Safety-Guardrailsv2.0
Local Data
Linked Snippet
Propagating v2.0
Purpose
Why workspaces exist
Workspaces prevent the platform from turning into one undifferentiated pile of content. They let teams separate ownership, permissions, review policy, and delivery targets in a way that mirrors real organizational boundaries.
A good rule is this: if two groups would not normally share the same release process or repository destinations, they should probably live in different workspaces.
Knowledgebase portfolio
A workspace can contain multiple knowledgebases. That lets one team manage several content domains while keeping them under a common operational model.
Destinations and policy
Export targets and release rules are anchored at the workspace level because publishing is an operational concern, not just a content concern.
Practical guidance
How to decide workspace boundaries
Use workspaces to reflect release ownership first, not org charts alone. A Support workspace might contain a customer-help KB and an internal escalation KB. A Platform workspace might manage runbooks, operational standards, and AI assistant policy content.
Avoid creating too many small workspaces too early. Fragmentation at the workspace layer can make reuse harder. Start with the smallest number that still preserves clear ownership and policy.
Next move
Set the operational boundary first, then add content.
When a workspace is well-defined, everything downstream becomes simpler: roles, release policy, destination mapping, and long-term knowledge ownership.