Access Management
What are User Roles?
User Roles define access permissions and functional capabilities for system users. Role-based access control (RBAC) ensures users can only access features and data appropriate to their responsibilities, maintaining security and operational integrity.
User Role Capabilities
Access Control:
Feature and menu access permissions
Data visibility restrictions
Entity modification rights
Report and export permissions
Functional Authorization:
Workflow execution rights
Approval authority limits
Configuration change permissions
Admin Panel access levels
Data Segmentation:
Department-based visibility
Geographic restrictions
Product line access
Customer segment access
Audit and Compliance:
Action logging by role
Permission change tracking
Segregation of duties enforcement
Regulatory compliance support
Permission Types
Feature Permissions
Control access to system features:
Application management
Loan servicing
Product configuration
Workflow design
Reporting and analytics
Admin Panel sections
Data Permissions
Control data visibility and modification:
View: Can see data
Create: Can add new records
Update: Can modify existing records
Delete: Can remove records
Export: Can download data
Approval Permissions
Define approval authority:
Approval amount limits ($0 to unlimited)
Product type restrictions
Risk category restrictions (can approve Green only, or Yellow and Green)
Geographic limitations
Configuration Permissions
Control system setup access:
Product creation and modification
Workflow design
Template management
Integration setup
User management
Role Assignment
Users can have:
Single Role: Most common, clear responsibility boundaries
Multiple Roles: For users with hybrid responsibilities (e.g., Underwriter + Collections Officer)
Temporary Role Elevation: For exception handling or coverage (e.g., temporary Manager access)
Department-Based Routing
Roles integrate with department routing:
Department Assignment:
Applications route to specific departments
Manual review assigned by department
Workflow results route based on outcome
Department Roles:
Underwriting Department: Underwriters
Collections Department: Collections Officers
Operations Department: Processors
Management: Managers
Role Hierarchies
Some roles have hierarchical relationships:
Escalation Path:
Application Processor
└── Underwriter
└── Operations Manager
└── Credit Risk Manager
└── ExecutiveHigher levels can override decisions of lower levels and access all data visible to lower levels.
Segregation of Duties
Critical roles are separated:
Cannot Combine:
Application Processor + Approver (same person enters and approves)
Workflow Designer + Underwriter using workflow (designer might bias decisions)
Collections Officer + Write-off Authority (prevents premature write-offs)
System enforces these separations through role incompatibility rules.
Implementation Resources
Through SDK (Development team)
Role Structure: Data Model Setup - Define role entities and permissions
Access Control: Getting Started - Implement RBAC logic
Through Admin Panel
User Management: User Management - Create and assign user roles
Role Configuration: Core Configuration - Define role permissions
Department Setup: Workflow Management - Configure department routing
Related Topics
Applications - Role-based application access
Status Management - Role-based status transitions
Manual Review - Role-based review routing
System Operations - Role-based operational access
TimveroOS: Role-based access control for lending operations
Last updated
Was this helpful?