🚚 Miễn phí giao hàng toàn quốc

✅ Tặng Gói Hỗ trợ online trọn đời

✅ Giá cạnh tranh nhất thị trường

✅ Miễn phí tư vấn giải pháp

🚚 Miễn phí giao hàng toàn quốc

✅ Tặng Gói Hỗ trợ online trọn đời

✅ Giá cạnh tranh nhất thị trường

✅ Miễn phí tư vấn giải pháp

Hotline: 0943.199.449

Địa chỉ: Tầng 1, tòa nhà Deli, 75 Hoàng Văn Thụ, P. Cầu Kiệu

Bitrix24 Helpdesk

Access permissions conflict in CRM

This article explains how to use access permission roles and types to avoid conflicts. For more details on CRM access permissions and setup, see:
Access Permissions in CRM

Roles in CRM

Roles fall into two categories:

  1. Personal role: Assigned to a specific employee.
  2. Group role: Assigned to a group, such as a department, workgroup, or project.

Access permission types

<

Access permissions can be detailed or inherited.

Detailed permissions apply to all items and stages.

Inherited permissions apply only to item stages. Instead of setting permissions for each stage, the stage follows a general rule.

By default, all stage permissions are inherited. They do not depend on the previous stage. They follow the general rule set for the action applied to the item.

First, define a general rule for an action, such as who can read or edit an item. Then choose one of the following for each stage:

  • Use the general rule — Inherit. The stage follows the general rule. For example, if Read is set to All, all stages with Inherit also allow access for All.
  • Set custom permissions. If you select a different value for a stage, it overrides the general rule.

Overlapping access permissions

To review overlapping permissions:

  1. Select an employee in the field next to the search bar.
  2. Check the slider that shows their assigned roles.

This view helps you understand how permissions combine and lets you adjust them if needed.

Roles In this example, an employee has two types of roles with different access levels.

Avoid permission conflicts

Follow these best practices:

Set personal permissions
Use personal permissions for small CRM teams instead of group roles.

Assign permissions from top to bottom
Start with main departments, then configure subdepartments.

Create separate roles for each department
Avoid using the All department and subdepartment employees option. Create separate roles for each subdepartment instead.

Avoid the Employee and supervisors role
If you select a user in the Departments tab, they appear with the Employee and supervisors role. Avoid using this role. It can cause conflicts for supervisors.

Use inherited stage permissions
If item and stage permissions match, select Inherit instead of setting each stage manually. A large number of roles and permissions can slow down the CRM.

Resave CRM items after structure changes
If you move an employee to another department, resave their CRM items. This ensures permissions update correctly.
Access problems after editing the company structure

Was this information helpful?
Thank you for your feedback.
Get Implementation Help from a Partner
That's not what I'm looking for
Complicated and incomprehensible text
The information is outdated
It's too short. I need more information
I don't like the way this tool works
Get your Bitrix24 set up by local professionals
FIND BITRIX24 PARTNER NEAR ME
implementation_helper_man
Go to Bitrix24
Don't have an account? Create for free
Related articles
Inventory access permissions: Control who can edit selling prices Inventory access permissions Configure import and export permissions Configure access permissions to change product prices in CRM forms Set permissions for product form layout Set permissions to control product visibility in the online store Role-based access permissions in CRM
Zalo
0943.199.449