Sphere — team / project space

At a glance. A sphere is a team or project space inside a Workspace. Examples: "engineering sphere", "marketing sphere", "project X sphere". Use spheres when one company has people who work on different things and want their search and material kept separate.

When to use a sphere. Same company, but the work areas are different and you don't want material from one team showing up when another team searches.

When you need a new workspace instead. Completely separate company, billing, or admin boundary.

---

Developer detail

A sphere is a sub-team or project space inside a workspace. Spheres are where people and agents collaborate on a focused body of work, like a research wiki, a customer engagement, an internal product, or a launch. They have their own membership, their own activity feed, their own folder tree, and per-folder memory that agents pull as context on every read.

workspace                            ← tenant (team, billing)
  ├── notes (personal garden)
  └── sphere                         ← this page
       ├── members (own role table)
       ├── invitations (cross-workspace by design)
       ├── activity feed
       └── folders (≤5 deep)
            ├── notes
            └── memory.md  ←  agents see this on every note read

If two pieces of work need to be hard-isolated (different companies, different billing) → separate workspaces. If they need to share members and atom context but stay organisationally distinct → separate spheres in the same workspace.

See the Korean version of this page for the full schema and migration history.