Workspace roles
Workspace-aware identity for SaaS products and customer portals.
Give every customer workspace clean Project roles, secure sessions, signed events, and audit trails without rebuilding access logic for each account.
Project member access
Signed webhooks
Audit logs
A SaaS identity path from customer account to lifecycle signal.
Model the customer relationship once, then let product access, admin visibility, events, and growth workflows inherit the same context.
Workspaces
Represent customer organizations, teams, or accounts with clear ownership.
Projects
Separate product lines, environments, and customer-facing surfaces.
Members
Keep Team Member console access distinct from Project Member runtime access.
Events
Attach sessions, webhooks, and audit records to the same identity model.
Growth
Use lifecycle context for expansion, onboarding, and customer health.
Role-aware customer portals
Customer admins, members, and support operators can map to different access surfaces without collapsing every user into one role.
- Workspace roles
- Project roles
- Environment-aware access
Events that stay tied to identity
Sessions, signed webhooks, and audit entries stay connected to the workspace and project that produced them.
- Signed webhooks
- Session visibility
- Audit trails
Growth signals with guardrails
Lifecycle and usage signals can support onboarding and expansion while keeping policy and audit close to the relationship.
- Lifecycle context
- Plan-aware limits
- Policy visibility
Start with one customer workspace model.
Create a workspace, connect one Project, and give your SaaS product a cleaner identity foundation before access logic spreads.
- Workspace roles
- Project member access
- Signed webhooks
- Audit logs