Role Profiles Module Documentation
Table of Contents
- Module Overview (Technical)
- Module Overview (Commercial/Business)
- Module Overview (End User/Administrator)
- Configuration Sections
- Settings Reference
- Common Scenarios & Examples
- Limitations & Important Notes
- Troubleshooting Tips
- Glossary
---
1. Module Overview (Technical)
What Are Role Profiles?
Role Profiles is a permission management module that defines access levels for admin panel users. Each role profile contains a permissions matrix specifying access (Full Control, Read Only, No Access) for every module in the system.
Architecture
Key Tables
| Table | Purpose | |
|---|---|---|
public.role_profiles | Role definitions | |
public.role_permissions | Permission matrix |
Key Files
| File | Description |
|---|---|
modules/roleProfiles/ | Frontend module |
2. Module Overview (Commercial/Business)
Business Value
Role Profiles provides granular access control:
| Without Role Profiles | With Role Profiles | |
|---|---|---|
| All or nothing | Granular control | |
| Single admin type | Multiple roles | |
| No customization | Custom permissions | |
| Security risk | Least privilege |
Use Cases
- Operator Role
- Limited system access
- Support Role
- No configuration changes
- Department Admin
- Restricted system settings
- Auditor Role
- Compliance review
Feature Highlights
| Feature | Benefit | |
|---|---|---|
| Permissions Matrix | Per-module control | |
| Three Levels | Full, Read, None | |
| Custom Roles | Create any role | |
| User Assignment | Link profiles to users | |
| Inheritance | Visual inherited markers | |
| Duplicate | Clone and modify |
3. Module Overview (End User/Administrator)
What Can You Do?
- Create custom role profiles
- Set permissions per module
- Choose Full Control, Read Only, or No Access
- Assign profiles to users
- Duplicate existing profiles
- Search and filter permissions
Role Profiles Interface
Create/Edit Role Profile
Quick Tips
TIP
Duplicate: Clone existing profile as starting point.TIP
Search Modules: Find specific modules quickly.WARNING
Users Assigned: Cannot delete profile with assigned users.---
4. Configuration Sections
Basic Information
| Field | Description | |
|---|---|---|
| Profile Name | Display name | |
| Description | Purpose explanation |
Permissions Matrix
| Column | Description | |
|---|---|---|
| Module | System module/feature | |
| Full Control | Create, read, update, delete | |
| Read Only | View only, no changes | |
| No Access | Hidden from user |
5. Settings Reference
Permission Levels
| Level | Icon | Capabilities | |
|---|---|---|---|
| Full Control | ● | Create, Read, Update, Delete | |
| Read Only | ● | Read only | |
| No Access | ● | Hidden |
Module Groups
| Group | Modules | |
|---|---|---|
| Dashboard | Main dashboard, widgets | |
| Telephony | Extensions, Ring Groups, Queues | |
| Routing | Inbound, Outbound, IVR | |
| Gateways | Trunks, Carriers | |
| Reports | CDR, Statistics | |
| System | Settings, Users, Profiles |
Default Profiles
| Profile | Description | |
|---|---|---|
| Administrator | Full access to everything | |
| Operator | Day-to-day operations | |
| User | Basic read access |
6. Common Scenarios & Examples
Scenario 1: Create Operator Role
- Click "Create Profile"
- Name = "Operator"
- Description = "Day-to-day operations"
- Set Extensions = Full Control
- Set Ring Groups = Full Control
- Set System Settings = No Access
- Set Users = No Access
- Save
Scenario 2: Read-Only Auditor
- Click "Create Profile"
- Name = "Auditor"
- Set all modules = Read Only
- Save
Scenario 3: Duplicate and Modify
- Find existing profile
- Click Duplicate
- Rename to new name
- Adjust permissions
- Save
Scenario 4: Department-Specific Role
- Create new profile
- Name = "Sales Manager"
- Full Control: Extensions, Queues, CDR
- Read Only: Ring Groups
- No Access: System, Gateways
- Save
---
7. Limitations & Important Notes
Technical Notes
NOTE
User Assignment: Delete users or reassign before deleting profile.NOTE
Menu Visibility: No Access hides menu items.WARNING
System Profiles: Some profiles may be protected.Best Practices
- Least Privilege: Grant minimum required access
- Document Roles: Describe each profile purpose
- Regular Review: Audit permissions periodically
- Use Inheritance: Build on existing profiles
- Test Roles: Verify access before deployment
Permission Precedence
| Scenario | Result | |
|---|---|---|
| Full Control selected | All operations allowed | |
| Read Only selected | View only | |
| No Access selected | Module hidden |
8. Troubleshooting Tips
Common Issues
| Symptom | Possible Cause | Solution | |
|---|---|---|---|
| Can't delete profile | Users assigned | Reassign users first | |
| Menu not visible | No Access set | Grant Read or Full | |
| Can't edit | Read Only access | Need Full Control | |
| Search not working | Wrong module name | Check spelling |
Check Profile Assignments
Verify Permissions
- Assign role to test user
- Login as test user
- Verify menu visibility
- Test create/edit operations
---
9. Glossary
| Term | Definition | |
|---|---|---|
| Role Profile | Permission set | |
| Permissions Matrix | Module access grid | |
| Full Control | Complete access | |
| Read Only | View only access | |
| No Access | Hidden/blocked | |
| Inheritance | Permission from parent |
Lua Script Status ℹ️
Admin Module
| Component | Status |
|---|---|
| Role Profiles | ℹ️ Admin panel module - no Lua handler required |
---
Documentation last updated: January 2026