Schematex
erd·Crow's-foot ERD·software, business·complexity 3/3·since v0.4.0

Multi-tenant SaaS RBAC schema

Crow's-foot ERD for tenants, users, memberships, roles, permissions, invitations, and audit events in a SaaS workspace product.

For the SaaS backend engineer

Open in Playground →
erd·§
↘ preview
100%
SaaS RBAC Entity-Relationship Diagram with 8 entities and 9 relationships. SaaS RBAC belongs to joins has role scoped to Tenant tenant_id uuid PK name varchar * plan varchar User user_id uuid PK email varchar UK name varchar Permission permission_id uuid PK key varchar UK Role role_id uuid PK tenant_id uuid FK name varchar * Invitation invitation_id uuid PK tenant_id uuid FK email varchar * AuditEvent event_id uuid PK tenant_id uuid FK actor_user_id uuid FK Membership tenant_id uuid PK FK user_id uuid PK FK role_id uuid FK status varchar * RolePermission role_id uuid PK FK permission_id uuid PK FK
UTF-8 · LF · 53 lines · 1534 chars✓ parsed·1.4 ms·16.7 KB SVG

Scenario

RBAC schemas are where generic ERD examples stop being useful. A SaaS product needs tenant scoping, composite keys on join tables, optional actor references for system events, and non-identifying edges for nullable audit metadata.

Annotation key

ERD syntax