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

User vs account vs organization

A User is a person; an Organization is the tenant. Permissions live on the Membership that joins them — never on the user by itself.

01

What this skill helps you build

The core SaaS identity model: a person is a User, the tenant is an Organization, and a Membership joins them — so you authorize through membership, not the user alone.

The production takeaway

A User is a person; an Organization is the tenant. Permissions live on the Membership that joins them — never on the user by itself.

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

The identity foundation every B2B SaaS app rests on: a clean separation between a User a real person with login credentials , an Organization the tenant that owns data and pays the

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

Reach for this model the moment more than one person can ever share data, or one person can ever belong to more than one workspace. Concretely: You sell to teams, not just individu

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

Three distinct concepts get muddled into the word "account." Keep them apart: User — a person. Has an email, a password or SSO identity , and a session. A user is the same human ac

🔒
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.