Products / Tenant identity
Give each business customer a clear administrative boundary for members, groups, SSO, provisioning and tenant-level policy.
Explore the design intent, review practical decisions and validate exact behavior against your deployed configuration.
Why it matters
B2B products often mix platform administration with customer-tenant administration. The wrong boundary can expose one tenant to another or grant a customer administrator platform-wide authority.
Design intent
Model tenant membership explicitly, assign tenant-scoped roles, and expose only the configuration a tenant administrator is allowed to manage. Treat domains, SSO, SCIM and tenant network rules as separate policy surfaces.
Worked scenario
A tenant admin invites a member and manages a SAML connection for their organisation without gaining control over unrelated tenants.
Boundary to verify
Confirm enforcement at the relevant server, API, resource or operational decision point. A hidden button or an informative dashboard is not, by itself, an authorization control.
Practical path
Use these stages as a review guide. Exact settings and enforcement points depend on the configured deployment and connected systems.
Identify the actor, target resource and operation that b2b saas is meant to govern.
Model tenant membership explicitly, assign tenant-scoped roles, and expose only the configuration a tenant administrator is allowed to manage. Treat domains, SSO, SCIM and tenant network rules as separate policy surfaces.
A tenant admin invites a member and manages a SAML connection for their organisation without gaining control over unrelated tenants. Also test the path that should be denied, deferred or sent for review.
Check that the resulting state is understandable and that the decision can be investigated later. For audit-enabled operations, confirm the relevant actor and context are captured.
Before rollout
A capability is easier to operate when ownership, failure behavior and verification are defined upfront.
This page describes a design approach based on WebFrolic’s documented product model. Verify feature availability and exact behavior in your environment before relying on it for a control requirement.
Related capabilities
Follow the related areas to understand how this capability fits within identity, access, lifecycle and operations.
Evaluate with your scenario
Share the identities, resource boundary and decision you want to test. The walkthrough can focus on the relevant behavior rather than a generic feature tour.
