SKILL-099 Teams, organizations, and multi-tenancy Locked skill

Workspace switching

The active workspace is server-side state, re-checked for membership on every request — never trust an org id sent by the client.

01

What this skill helps you build

Let users who belong to several organizations switch the active workspace — and re-verify their membership and permissions on every request.

The production takeaway

The active workspace is server-side state, re-checked for membership on every request — never trust an org id sent by the client.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

Teams, organizations, and multi-tenancy
What this helps you build

A reliable workspace switcher : the dropdown in your app shell that lets a user who belongs to several organizations pick which one they're currently working in — and the server si

🔒
Teams, organizations, and multi-tenancy
When to use this

Use this the moment a single user account can belong to more than one organization, team, or workspace. That's nearly every B2B SaaS: A consultant who is a member of several client

🔒
Teams, organizations, and multi-tenancy
The core idea

The current workspace is server side state . It lives in the session or is encoded in the URL and validated server side , not in a value the browser is trusted to assert. Switching

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.