Grant only the access each role actually needs.
Use a user-to-role-to-permission model where API guards and frontend checks rely on a flattened effective permission list returned for the signed-in user.
Role-Based Permissions
01Define permissionRole-Based Permissions process stepActive
02Add to roleRole-Based Permissions process stepActive
03Assign roleRole-Based Permissions process stepActive
Role-Based Permissions workflows that stay connected.
Use a user-to-role-to-permission model where API guards and frontend checks rely on a flattened effective permission list returned for the signed-in user.
Permission naming
Permissions follow a clear module.action convention such as users.manage or audit.view.
Backend enforcement
JwtAuthGuard verifies identity and PermissionsGuard enforces required module permissions.
Frontend awareness
The authenticated user payload exposes permissions for role-aware menus and actions.
Role-Based Permissions work stays structured from setup to review.
Use a user-to-role-to-permission model where API guards and frontend checks rely on a flattened effective permission list returned for the signed-in user.
- Define permission
- Add to role
- Assign role
- Read effective list
Role-Based Permissions controls keep records clean and traceable.
Choose a view to see how this module keeps daily HR work structured and reviewable.
Naming
Module-action permission names make access rules understandable during role setup.
Values remain traceable in HRM.Details that make role-based permissions dependable.
Granular permission model
Access is controlled at the module action level.
Default role coverage
Seeded roles provide a working starting point for common HRM teams.
Custom roles
Administrators can create focused roles for real operational responsibilities.
Guarded backend
API actions remain protected even if a UI element is hidden incorrectly.
Frontend permission list
Client UI can adapt to the signed-in user's effective permissions.
No deny rules
The model stays additive: access is granted by assigned roles.
Role-Based Permissions works with the rest of HRM.
Access Control
Shared context keeps this workflow aligned with access control records.
ConnectedRole-Based Permissions
Shared context keeps this workflow aligned with role-based permissions records.
ConnectedAudit Logs
Shared context keeps this workflow aligned with audit logs records.
ConnectedSystem Administration
Shared context keeps this workflow aligned with system administration records.
ConnectedEmployee Documents
Shared context keeps this workflow aligned with employee documents records.
ConnectedWhat HR teams usually ask about role-based permissions.
They follow a module.action naming style.
The user gets the union of both roles' permissions.
No. Backend guards enforce protected actions.
See how role-based permissions fits your HR operation.
Map your current workflow to the right HRM setup, permissions and rollout plan.