To support flexible permission allocation, administrators can add custom Roles based on actual business scenarios, such as project implementation personnel or material procurement staff.

1. Creating Business Roles

Administrators can create new business Roles under “System Management - Role & Permission Management - Business Function Permissions.”

• Business Roles can be assigned to front-end staff for CRM operations. For example, a Sales Role may grant access to view Accounts and Sales Orders.

picture coming soon:

2. Role Permission Configuration

2.1 Object Function Permissions

Business Roles define specific operational permissions for CRM objects.

• List View Access: Controls visibility of object list entries. If disabled, employees won’t see Leads in their dashboard.
• Detail View Access: Grants access to object detail pages. Without this, employees cannot view Lead details.
• Action Permissions: Enables operations on business data. Disabling “Create,” “Edit,” or “Import” hides these buttons on list/detail pages.
• Note: Disabled objects do not appear in Role permission settings.

picture coming soon:

2.2 Field-Level Permissions

Roles can restrict field access (read, edit, export). For example:
- Hide customer phone numbers from telemarketers.
- Conceal Sales Order amounts from service teams.

• Read: Allows field visibility in Create/Edit/List/Detail pages.
• Edit: Permits field value modification in Create/Edit pages.
• Export: Enables field export from List pages.

2.3 Assigning Roles to Employees

Under “System Management - Role Permission Settings,” administrators can:
- Assign Roles to employees (multiple Roles per employee; permissions are cumulative).
- Add Employees: Assign Roles to new users (e.g., onboarding sales staff with the “Sales” Role).
- Edit Roles: Modify existing Role assignments.
- Remove: Revoke all non-admin Roles (removes CRM access if no Roles remain).
- Copy Roles: Replicate one employee’s Roles to another.
- Primary Role: Determines layout/type display for employees with multiple Roles in custom objects.
- Special Logic:
- “CRM Admin” assignments require “Management Function Permissions.”
- “All Employees” is a system-wide default Role (not displayed in user assignments).

2.4 Approval Permission Settings

Assign approval Departments to employees with specialized approval Roles. Example:
- Manufacturing firms may route Sales Order approvals to finance staff based on production lines.

• Edit Approval Departments: Select Departments for which the employee is responsible.