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

Tenant routing

Resolving the tenant is not authorization — after you find the tenant, you must still verify the current user is a member of it.

01

What this skill helps you build

Map subdomains, URL paths, and custom domains to a tenant, resolve it early in the request, and verify the current user belongs to it.

The production takeaway

Resolving the tenant is not authorization — after you find the tenant, you must still verify the current user is a member of it.

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 way to figure out which tenant a request is for — from acme.app.com , app.com/acme , or a customer's own dashboard.acme.com — and to make that tenant available to the re

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

Reach for tenant routing the moment a single deployment serves more than one customer organization and you need to know which one on every request: A B2B SaaS where each company ge

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

Two steps that must not be confused: resolve , then authorize . 1. Resolve the tenant from the request as early as possible — from the host subdomain or custom domain or the URL pa

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