Roles and Permissions are the foundation of RISPER CRM.
Before starting daily operations, it is mandatory for the Owner or App Administrator to configure roles and permissions according to the organization’s operational workflow.
Incorrect or incomplete role configuration may lead to access issues and confusion. In most cases, when users feel “the software is not working,” it is due to improper role and permission setup, not a system issue.
Why Roles & Permissions Are Critical
- Controls who can access what
- Defines responsibilities for each user
- Protects sensitive data
- Ensures smooth workflow across departments
- Aligns CRM behavior with your real business operations
Accessing Roles & Permissions
- Log in as Owner / App Admin
- Go to Settings → Roles & Permissions
- Click Add Role to create a new role
Creating a Role
While creating a role:
- Enter the Role Name
Examples: - Front Desk
- Manager
- Supervisor
- Team Leader
Once saved:
- The role will appear in the role list
- On the right side, click the Permissions button to configure access
Understanding the Permissions Screen
After clicking Permissions, a detailed permissions panel will open.
Permission Structure
Each permission row contains:
- Module Name (Employees, Projects, Tasks, Attendance, etc.)
- Add
- View
- Update
- Delete
Each action has selectable access levels such as:
- All
- Added
- Assigned
- Added & Assigned
- None
Permission Types Explained (Core Logic)
1. Add Permission
Controls whether the user can create new records.
Options:
- All – Can add records in this module
- None – Cannot add records
Example:
If “Add → Employees” is set to All, the user can add new employees.
If set to None, the user cannot add employees.
2. View Permission (Most Important)
Controls what data the user can see.
Options:
- All
- Added
- Assigned
- Added & Assigned
- None
Meaning of Each Option:
- All
User can see all records in that module. - Added
User can see only the records they created. - Assigned
User can see only records assigned to them. - Added & Assigned
User can see:
Records they created
Records assigned to them by others
- None
User cannot see any records.
3. Update Permission
Controls whether the user can edit or change status of records.
This includes:
- Clicking Save
- Changing task status (To Do → In Progress → Completed)
- Updating project stages
- Updating invoice/payment status (Unpaid → Paid)
Options:
- All
- Added
- Assigned
- Added & Assigned
- None
4. Delete Permission
Controls whether the user can delete records.
Options:
- Yes – Can delete records
- Added - Can delete his or her own added records
- None – Cannot delete records
Detailed Module Examples
Example 1: Employees Module
Scenario: Supervisor Role
Add
All → Supervisor can add new employees
View
Added & Assigned
Supervisor can see:
Employees they added
Employees assigned under them
Update
- Assigned
Supervisor can update employee details only for employees assigned to them - Can delete records
- None
Supervisor cannot delete employees
Example 2: Projects Module
Scenario: Project Manager Role
Add
All
Can create new projects
View
All
Can see all projects in the system
Update
Added & Assigned
Can:
Update projects they created
Update projects assigned to them
Delete
None
Cannot delete projects
Use Case Example
Project status change from Planning → In Progress → Completed
Only users with Update permission can change these stages
Example 3: Tasks Module
Scenario: Team Member Role
Add
Assigned
Can add tasks only within assigned projects
View
Assigned
Can see only tasks assigned to them
Update
- Assigned
Can update: - Task status
- Task progress
- Task remarks
Delete
- None
Cannot delete tasks
Use Case Example
- Task moves from To Do → In Progress → Completed
- User can only update tasks assigned to them
- Advanced Permissions (More Button)
- Each module has a More button on the right side.
What It Does:
Breaks the module into sub-permissions
Example:
- Project Files
- Project Members
- Task Comments
- Task Attachments
Each sub-permission allows:
- Add
- View
- Delete
- None
This gives very granular control over user actions.
Best Practices for Role Setup
Always define roles before adding employees
Create roles based on real operational responsibilities
Avoid giving All permissions unless required
Test roles using a dummy user
Review permissions periodically
Common Mistakes
Skipping role setup during implementation
Giving incorrect View or Update permissions
Assuming default roles will work for all businesses
Support & Assistance
Roles & Permissions setup is a crucial configuration step.
If you need help:
Raise a Support Ticket
Request an Online Meeting
During implementation, our team will assist you end-to-end
Our goal is to ensure your business operation style aligns perfectly with RISPER CRM, so the system works smoothly and efficiently.