Switchy
Sign up
Concepts

Workspaces

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

Mental model

An org is your team's account. A Project is a container of scoped memory, Slack/Teams channel mappings, and tasks - one per topic or body of work. A session is one chat thread inside a Project. Members belong to the org and have access to specific Projects.

Key properties

  • Every signup creates an org. Solo users have an org of one - every feature works the same.
  • A Project lives inside exactly one org. Memberships are explicit: you join a Project; org membership alone doesn't grant access.
  • A session belongs to exactly one Project. Real-time fan-out happens at the session level via Ably.
  • Org roles: OWNER, ADMIN, MEMBER. Project 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 Project per client or workstream. A consultant has Projects named for each client; everyone they've invited from that client sees only theirs.
  • One Project per recurring meeting. The standup Project accumulates context week over week - last week's blockers, this week's focus.
  • One Project for the whole team. Smaller teams skip the per-project split entirely.

What this isn't

A Project 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 Project is open in a browser tab. Use email or your existing tools when you need someone's attention now.

A Project 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

←PreviousWelcomeNextMemory→