---
title: "Five Checkpoints for a B2B SaaS Tenant Foundation"
description: "A five-checkpoint walkthrough of what a B2B SaaS tenant actually needs: provisioning, identity and session defaults, per-tenant data isolation, agent access, and localized governance."
---

# Five Checkpoints for a B2B SaaS Tenant Foundation

**Type:** [How to](https://yomu.fyi/visual-explainers/category/how-to.md)

![Numbered five-step vertical flow on a light blue paper background: Provision the tenant bundle, Lock session defaults, Scope every request, Extend to agents, and Localize governance, each in a bordered panel with a short outcome label.](https://yomufyi.s3.us-east-1.amazonaws.com/visual-explainers/c1089845-56cb-49d9-a376-19764da5759b/image-6025e68f-ee8d-4add-9a5a-71708fbf9a75.webp)

> A five-checkpoint walkthrough of what a B2B SaaS tenant actually needs: provisioning, identity and session defaults, per-tenant data isolation, agent access, and localized governance.

## Explanation

A B2B SaaS product is not multi-tenant just because it has an organizations table. This explainer walks through five checkpoints that turn a customer organization into an isolated, governable tenant: provisioning the tenant bundle of application, API, roles and SSO connections; locking token and session defaults; scoping every request to one tenant with row-level security; extending the tenant boundary to agents that act as the signed-in user; and adding regional consent and org-level spend limits. Each checkpoint names the outcome you should be able to demonstrate before moving on.

## FAQ

### Why isn't an organizations table enough for multi-tenancy?

Tenancy is enforced per request. Supabase's .NET SDK attaches auto-refreshed tokens to each call so row-level security decides what a user sees, and its MCP server block runs every tool call as the signed-in user. Publishable and anon keys are safe for clients, but secret and service keys bypass row-level security and belong on the server.

### How much of a tenant setup can be declared as code instead of clicked?

Auth0's Terraform modules turn the foundation into modules: one b2b-saas-starter block creates an application, API, tenant settings, attack protection and MFA, defaulting to RBAC, PKCE, rotating refresh tokens and TOTP MFA. Roles, permissions and enterprise SSO connections are described as data and validated, every default can be overridden, and extra apps can skip tenant-wide resources.

### What breaks first when agents start acting inside a customer tenant?

Client onboarding, not model quality. Auth0's CIMD support lets agent clients register dynamically from an HTTPS metadata URL, and Application Profiles apply refresh token rotation and DPoP across those clients without manual review. Governance layers such as JetBrains Air Governance add org-level caps on agents, models and spend so dynamic clients stay accountable.

**Tags:** [B2B](https://yomu.fyi/topic/b2b.md), [B2B SaaS](https://yomu.fyi/topic/b2b-saas.md), [MCP](https://yomu.fyi/topic/mcp.md), [Multi-tenant](https://yomu.fyi/topic/multi-tenant.md), [RBAC](https://yomu.fyi/topic/rbac.md), [SSO](https://yomu.fyi/topic/sso.md)

## Related reading

### [Getting started with the Supabase .NET SDK](https://yomu.fyi/post/getting-started-with-the-supabase-net-sdk.md)
- Company: [Supabase](https://yomu.fyi/company/supabase.md)
- Author: guillaume\_faas
- Published: Oct 26, 2026
- Type: Tutorial

The Supabase .NET SDK provides a single C# client for Auth, Database, Storage, Realtime, and Edge Functions; version 8.0.0 moves serialization to System.Text.Json and adds injectable HttpClient with retry. It also ships a dependency injection package for ASP.NET Core that registers the client as scoped via IHttpClientFactory to pool connections. Models derive from BaseModel with table and column attributes; queries use From () with Where filters, and updates require explicit calls without a change tracker, supporting both model-based and query-builder approaches. Authentication covers email/password, OAuth, magic links, phone, and SSO, with auto-refresh tokens attaching to subsequent requests for Row-Level Security. Setup for ASP.NET Core uses AddSupabase, while other apps construct the client manually and call InitializeAsync; the post also distinguishes publishable and anon keys for client apps from secret and service keys that bypass Row-Level Security.


### [Air Governance: Manage AI Agents, Access, and Spend Throughout Your Organization](https://yomu.fyi/post/air-governance-manage-ai-agents-access-and-spend-throughout-your-organ.md)
- Company: [Jetbrains](https://yomu.fyi/company/jetbrains.md)
- Author: Viktor Kiselev
- Published: Oct 22, 2026
- Type: Announcement

JetBrains Air Governance, formerly JetBrains Central, is now generally available as the organization layer of JetBrains Air for managing agentic AI usage. It provides a single console to manage AI agents, models, and providers across teams, set spending limits, and track both costs and outcome metrics like the split between human-authored and AI-generated code. The tool works with Claude Agent, Codex, Gemini CLI, Junie, and other ACP-compatible agents across IDEs, CLI, web, and mobile, and supports multiple vendors without separate contracts. Admins can set AI credit limits per user, team, or service account, manage BYOK providers, approve agents, and configure MCP servers at the company level, combining these into policies for different groups. Air Governance is available to all JetBrains organizational customers with free and paid plans starting at USD 20 per developer per month, and it already manages usage for roughly 2,300 people at JetBrains.


### [Localizing compliance at scale: achieving South Korea’s ISMS certification](https://yomu.fyi/post/localizing-compliance-at-scale-achieving-south-korea-s-isms-certificat.md)
- Company: [Cloudflare](https://yomu.fyi/company/cloudflare.md)
- Author: Kabin Calan
- Published: Oct 22, 2026
- Type: Announcement

Cloudflare obtained South Korea’s ISMS certification after a ten-day audit by KISA-appointed auditors covering 80 controls. To comply with Korean consent laws, Cloudflare localized its sign-up page for South Korean users to display four separately listed consent items and disabled social sign-up so every account goes through that form. Country detection uses IP geolocation as a default but the user’s selected country overrides it to make the consent decision based on residency. The audit examined data flow diagrams and access controls across internal systems, websites, and the dashboard, and verified the exact wording of Korean consent notifications. ISMS certification is valid for three years with annual audits and adds a local layer atop global certifications, requiring over a year of preparation.


### [Give your Supabase app its own MCP server](https://yomu.fyi/post/give-your-supabase-app-its-own-mcp-server.md)
- Company: [Supabase](https://yomu.fyi/company/supabase.md)
- Author: raul\_barroso,gregnr,saxon\_fletcher
- Published: Oct 22, 2026
- Type: Tutorial

Supabase announced the MCP Server block that lets developers give their Supabase apps an MCP server, enabling customers to use app actions as tools from clients like ChatGPT or Claude after signing in with their existing account. Every tool call runs as that user, so RLS policies decide what each agent can access. The block adds an Edge Function using the official MCP TypeScript SDK and Supabase authentication helpers to verify tokens and provide a user-specific Supabase client. Developers write tool functions that can query RLS-protected tables, call database functions, or invoke Edge Functions, keeping business rules in the code the tool calls. The server can also display app UI inside the chat via MCP Apps, and the block includes a Copy agent prompt button and works with Cloudflare Workers and other Web-standard backends.


### [Scaling AI Agent Identity with CIMD and Application Profiles in Auth0](https://yomu.fyi/post/scaling-ai-agent-identity-with-cimd-and-application-profiles-in-auth0.md)
- Company: [Auth0](https://yomu.fyi/company/auth0.md)
- Author: Eric Wu
- Published: Oct 22, 2026
- Type: Announcement

The rise of AI agents and MCP-based ecosystems introduces identity challenges when onboarding numerous clients without manual overhead. Auth0 expands its Client ID Metadata Document (CIMD) support with two registration modes — manual pre-registration and dynamic registration — for OAuth clients. Manual pre-registration requires an administrator to submit a metadata URL for review and approval, while dynamic registration enables just-in-time client discovery during authorization flows. CIMD uses an HTTPS URL as the client identifier pointing to a metadata document with the client’s name, redirect URIs, and authentication methods; Auth0’s implementation uses shared caching to reduce database write pressure and support more dynamic clients without latency. Application Profiles centrally manage security policies such as refresh token rotation and DPoP across dynamically registered clients, aiming to provide a practical identity foundation for MCP servers and agentic applications.


### [Introducing Terraform Auth0 Modules](https://yomu.fyi/post/introducing-terraform-auth0-modules.md)
- Company: [Auth0](https://yomu.fyi/company/auth0.md)
- Author: Rajat Bajaj
- Published: Oct 22, 2026
- Type: Announcement

Teams building B2B SaaS on Auth0 repeatedly configure applications, APIs, M2M clients, MFA, attack protection, branding, custom domains, and enterprise SSO. The new Terraform Auth0 Modules package this foundation into ready-made modules, starting with the b2b-saas-starter module on the Terraform Registry. A single module block creates an application, API, tenant settings, attack protection, and MFA, with security defaults like RBAC enforcement, PKCE, rotating refresh tokens, and TOTP MFA. Roles, permissions, and enterprise SSO connections for customer organizations are described as data inside the module, which validates input to prevent errors. The module supports multiple applications per tenant by letting other instances skip tenant-wide resources, and each default can be overridden via module inputs.
