Permission Setting
Last updated
Last updated
Purpose: Enable users to create and manage permissions for various entities, including customers, suppliers, and products. This functionality allows for granular control over specific details such as customer data, contacts, contact logs, sales opportunities, contracts, and sales record.
Purpose: Controls access to specific customer data based on the user's relationship to the data (e.g., creator or assigned representative).
Creator: The person who initially created the customer record.
Customer Service Representative (CSR): The individual responsible for customer communication and support.
Account Executive (AE): The salesperson responsible for managing the customer relationship.
Shared User: Users to whom the customer's card is explicitly shared for collaboration.
View: Read-only access to customer data.
Edit: Modify customer information.
Delete: Remove customer records.
Merge: Combine duplicate records into one.
Share: Provide access to other users by sharing the customer card.
View Log: Check historical changes and actions performed on the customer record.
Purpose: Provides the ability to monitor and manage data at various organizational levels. This includes seeing how customer information flows across the organization.
All Users: Permissions apply to all users.
Specific User: Permissions granted based on individuals.
Specific Role: Permissions granted based on role.
Specific Department: Permissions granted based on department.
Defines how much information can be accessed based on hierarchical position.
Myself: Only data related to the user.
Superior: The user’s direct supervisor.
All Superiors: Access to all higher-ups in the organization.
Subordinates: Data access for those reporting to the user.
All Subordinates: Access to the entire team of subordinates.
HOD (Head of Department): Access to the department’s data.
Same Department: Access limited to users within the same department.
Same Role: Access to users with the same role, even if in different departments.
1.2 Operations (View, Edit, Delete, Merge, Share, View Log).
Purpose: Manages access to different features or functionalities within the CRM system's interface.
Add: Ability to create new customer records or entities.
Import: Upload data into the CRM system.
Export: Download data from the CRM system.
Manage Tag: Modify tags associated with customers.
Nearby Customer: Access to a function that identifies customers located nearby, likely for sales or support purposes.
The log is displayed as a timeline chart, with the time of occurrence shown on the left and the operation type and details displayed on the right. It can be filtered by log type through the operation type, by the creation time using the existing time filter, or by customizing the range with the "Time range" button. Additionally, the [Search log] search box is used to search for log content.
Purpose: Provide clear overview of who is granted specific permissions and grouping the data by different dimensions.
Purpose: This dimension provides an overview of the specific types of permissions assigned (e.g., Add, Edit, Delete) and to whom they are granted.
Remark:
Permission Type: The type of action or permission granted (e.g., View, Edit, Delete, etc.).
Scope: Defines who the permission applies to (e.g., specific user, role, department, all users).
Data Filtering: This refers to any restrictions applied to the data a user can access based on specific criteria (e.g., only data related to their department, subordinates, or specific customers).
Purpose: Shows the individual users and the specific permissions they have, along with the extent to which they can access or modify data.
Remark:
User: The specific person (e.g., Gloria, John).
Cross items (Penetration): Indicates how deep the user's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Have Permission: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the user can access based on filtering conditions (e.g., only customers from a specific region).
Purpose: Provides a role-based view of permissions, useful for managing large groups of users. It defines what permissions are granted to users based on their role in the organization.
Remark:
Role: Specifies the role (e.g., Account Manager, Support Engineer).
Cross items (Penetration): Indicates how deep the role's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Have Permission: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the role can access based on filtering conditions (e.g., only customers from a specific region).
Purpose: Provides a department-wide view of permissions, often used to grant broader access to users within a specific functional area (e.g., sales, support).
Remark:
Department: Specifies the department (e.g., Sales, Customer Support).
Cross items (Penetration): Indicates how deep the department's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Have Permission: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the role can access based on filtering conditions (e.g., only customers from a specific region).
Purpose: Allows permissions to be controlled based on the relation of the user to specific data fields (e.g., Creator, Account Executive). It helps in granting granular permissions to specific fields within customer records.
Remarks:
Relation Control: Defines the user’s relationship to the data (e.g., Creator, CSR, Account Executive).
Cross items (Penetration): Indicates how deep the department's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Have Permission: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the role can access based on filtering conditions (e.g., only customers from a specific region).
