Role-Based
Access Control
The permission layer that decides who can see, open, and use each part of the CRM. Combines user roles, plan-based module availability, and per-user feature assignments so access is controlled at both the account level and the module level.
Access Resolved Completely.
Not simple role labels. A layered model that checks plan eligibility, applies user assignments, and resolves into allowed modules, features, and routes. Permission becomes part of the actual application flow.
The system supports both broad-access users and tightly restricted users without breaking plan boundaries. A user cannot be granted a module that the subscription does not support.
Clear Boundaries.
Each role establishes the broad identity and purpose of the user inside the CRM. Roles are paired with plan eligibility and per-user assignments to create the final access map.
Super Admin is treated as the highest access level, not constrained by normal user-level assignments. This gives the business a reliable administrative fallback account with full visibility across the CRM.
Route-Level Protection
Permission is enforced both in the interface and at the route layer. Users cannot bypass restrictions by manually entering URLs.
The CRM uses allowed module, feature, and route maps to decide what appears in the sidebar. Restricted modules are hidden so users are not shown areas they cannot use.
If a user tries to open a restricted page through a direct URL, the CRM blocks the request based on the mapped feature permission for that route. Not just hidden. Actually blocked.
Modules map to feature keys, routes map to feature keys. A module is available when at least one mapped feature is allowed. Scalable across menus, pages, and application logic.
Critical routes like dashboard, account settings, and subscription support remain available regardless of module restrictions. Users are never locked out of basic account functions.
Each Handled Differently.
The CRM distinguishes between plan-based, user-based, and integration-based restrictions so access handling is informative instead of using one generic failure for every case.
Control Every Account
Access control is managed alongside user creation and editing. Admins create accounts, choose roles, set module access, and manage login credentials and security settings.
Create users, choose their role, and select which plan-enabled modules they can access. Assignments are stored as feature permissions and used to calculate the final access map.
When a user is disabled, the CRM invalidates active sessions for that account. Access is removed immediately, not just on the next login.
View recent sessions, authentication events, and activity logs. Understand who has access, who is actively using the system, and whether changes are needed.
Sales, operations, finance, admin, and support users share the same CRM without seeing the same application. Each sees only what they need.
User Identity
Eligibility
Assignment
Full Access
Mapping
Control
Protection
Reasons
Hard Locks
with Feature Access
with Session Kill
Activity Visibility
See Access Control in Action
Watch how Triplide gives every team member exactly the right access through layered roles, plan-based eligibility, and per-user assignments.
Book a Free Demo