> For the complete documentation index, see [llms.txt](https://helpdesk.getfly.vn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.getfly.vn/web-version/editor/access-control-and-permissions-setup.md). # Access Control and Permissions Setup Access Control and Permissions Setup Permissions play a critical role in Getfly CRM, enabling you to manage access rights and the use of the software effectively for each individual or user group. This ensures that you can: Protect Information: Limit unauthorized access to sensitive data, ensuring the safety of customer, partner, and company information. Improve Work Efficiency: Assign appropriate permissions based on the role and responsibilities of each user, helping them focus on their core tasks and optimize operational effectiveness. Enhance Transparency: Ensure that each user can only access and use features they are authorized for, promoting clarity and transparency in work processes. ## 1. How to Set Permissions To configure permissions, follow these steps: Go to Settings →User Permissions → Select Permission Group → Check the permissions in the setup table.
The Admin Permission Group is the highest-level group with all permissions enabled (this group only supports adding permissions and does not allow removal of any). The system supports group-based permissions, allowing you to configure permissions for different user groups. ## 2. Basic Permissions in the System | 1 | **Access** |

Allowed to access the Module – Function.
When this permission is selected, the Module – Function will appear on the system interface.

| | - | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | 2 | **Add** |

Allowed to add new entries.
Example: For the Customer Module – allows adding new customers…

| | - | ------- | -------------------------------------------------------------------------------------------------------------- | | 3 | **Edit** |

Allowed to edit existing entries.
Example: For the Customer Module – allows editing customer information.

| | - | -------- | ---------------------------------------------------------------------------------------------------------------------------- | | 4 | **Delete** |

Allowed to delete entries.
Example: For the Customer Module – allows deleting customers.

| | - | ---------- | ----------------------------------------------------------------------------------------------------------- | | 5 | **Approve** |

Allowed to approve – applies to Modules/Functions that support approval.
Example: Approve orders…

| | - | ----------- | -------------------------------------------------------------------------------------------------------------------- | | 6 | **Payment** | This permission allows users to process order payments. | | - | ----------- | ------------------------------------------------------- | | 7 | **View All** |

Permission to view all data.
Example: Admin can view all customer information…

| | - | ------------ | ------------------------------------------------------------------------------------------------- | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helpdesk.getfly.vn/web-version/editor/access-control-and-permissions-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.