What RBAC is
RBAC is a model for access control. A role is a named set of permissions. You assign a role to each user. SenseCrypt builds RBAC into the identity provider (IdP).
- A role holds a set of permissions.
- A user gets one or more roles.
- SenseCrypt enforces the roles centrally.
How RBAC works
You define roles in SenseCrypt. You assign a role to each user. SenseCrypt checks the role on each request. It grants or denies access from the role.
- Define roles for your application.
- Assign roles to users or groups.
- SenseCrypt checks the role at each request.
What you get
RBAC keeps access rules simple and clear. You change one role to update many users. Audit logs record each access decision. Multi-tenant isolation keeps each tenant's roles separate.
- One role change updates many users.
- Audit logs record each access decision.
- Multi-tenant isolation separates roles per tenant.
How RBAC fits your stack
RBAC works with the SenseCrypt standards. It applies to OIDC, OAuth 2.0, and SAML 2.0 flows. The user signs in by face login first. RBAC then sets the user's access.
- Use RBAC with OIDC, SAML, or OAuth.
- Combine RBAC with face login.
- Start a 30-day free trial, no card.
Frequently asked questions
Does SenseCrypt support RBAC?
Yes. SenseCrypt gives role-based access control. You assign roles to users. Each role grants a set of permissions.
How does RBAC work with face login?
The user signs in by face login. SenseCrypt then applies the user's roles. RBAC decides what the user can do.
Does RBAC work across tenants?
Yes. Multi-tenant isolation keeps each tenant separate. Roles stay within their own tenant.
Related