Workspaces

Orgs hold Spaces hold sessions. That's the whole hierarchy.

Mental model

An org is your team's account. A Space is a topic or project — like a Slack channel, but tied to a body of memory. A session is one chat thread inside a Space. Members belong to the org and have access to specific Spaces.

Key properties

• Every signup creates an org. Solo users have an org of one — every feature works the same.
• A Space lives inside exactly one org. Memberships are explicit: you join a Space; org membership alone doesn't grant access.
• A session belongs to exactly one Space. Real-time fan-out happens at the session level via Ably.
• Org roles: OWNER, ADMIN, MEMBER. Space roles: OWNER, EDITOR, MEMBER, VIEWER.
• Billing is org-scoped. Credit pool, plan, seats — all live on the org, never a single user.

Common patterns

• One Space per project. A consultant has Spaces named for each client; everyone they've invited from that client sees only theirs.
• One Space per recurring meeting. The standup Space accumulates context week over week — last week's blockers, this week's focus.
• One Space for the whole team. Smaller teams skip the per-project split entirely.

What this isn't

A Space is not a Slack channel. There's no presence-of-notification model. Messages aren't push-notified by default; teammates see live updates only when the Space is open in a browser tab. Use email or your existing tools when you need someone's attention now.

A Space is not a project-management board. There's no kanban, no due dates, no assignees. Switchy is the shared room around the work, not the work tracker.

Next

• Memory — how saved facts are scoped to a user, Space, or org.
• Agents — Claude, GPT, Gemini, MCPs.
• Create your first Space.