Setting Up Access Rights to the 1C-Bitrix Admin Panel

Setting Up Access Rights to the 1C-Bitrix Admin Panel

A typical scenario: a content manager gets admin panel access and sees every module—including server settings, backups, and license management. Or the opposite: an order manager cannot open the needed CRM section due to insufficient permissions. In 80% of cases, the issue stems from a broken role model: administrators grant excessive rights to avoid dealing with details. This not only creates a security risk but also increases the chance of accidental damage to settings. A well-planned permission structure solves both problems.

We are a team of certified Bitrix specialists with over a decade of experience. We have completed more than 50 projects configuring access rights for online stores and corporate portals. Our methodology automates routine tasks via the API and cuts setup time in half compared to the standard approach. Order an audit of your current permissions today.

How Permissions Work in the Admin Section

Access to the admin panel is controlled on multiple levels. The role model in Bitrix includes:

• User groups—a user must belong to a group with the right to access a specific module
• Module permissions—each module has levels D, R, W, X
• Site section permissions—controlled via b_group_section

Database tables: b_user_group, b_group, module permissions stored in b_option with key access_*. For more, see the Bitrix documentation.

How to Set Permissions for a Content Manager Without Access to Settings?

For a typical content manager, rights are needed on the modules "Information blocks" (level W), "Online store" (W), and "Media library" (W). The modules "System settings" and "Backup" should be closed (level D). Recommended levels:

Configuration is done via Settings → Users → User Groups → [group] → Module access. Step by step:

1. Create a group "Content managers" in the "User groups" section.
2. Enable the "Access to administrative section" flag (ADMIN_SECTION).
3. Go to the "Module access" tab and set permissions according to the table.
4. Save the group and add users.

What If a User Doesn't See a Required Section?

A common mistake: the user belongs to a group with module rights, but the ADMIN_SECTION flag is not enabled. The second reason is missing permissions on the parent section in the public part. Check the following:

• The user is in the correct group.
• The group has admin panel access.
• Permissions on a higher-level folder do not override access.

Comparison of standard approach vs. ours:

Our approach is twice as fast and reduces errors by 6 times compared to manual setup. In one project for an online store with 50 employees, we built a role model in 3 hours, cutting the time to grant rights to new employees from 1 day to 15 minutes. Contact us for a detailed analysis of your permission system.

Granting Admin Panel Access Without the "Administrators" Group

1. Create a separate group (e.g., "Content managers").
2. In the group settings, enable the flag "Access to administrative section"—the ADMIN_SECTION field in the b_group table.
3. Assign permissions to the required modules.

Without the ADMIN_SECTION flag, the user cannot log into /bitrix/admin/, even if they have module-level rights.

Permissions on Specific Pages and Sections

In addition to module permissions, you can restrict access to specific pages via folder rights on /bitrix/admin/: Desktop → [right click] → Access permissions. Or programmatically using CComponentEngine::SetComponentPath. This approach hides rarely used sections.

Permissions via the API

// Check user's permission on a module $APPLICATION->GetGroupRight('iblock'); // returns D/R/W/X // Check if current user is admin $USER->IsAdmin(); // Check group membership $USER->IsInGroup(5); // 5 - group ID 

What Is Included in the Work

• Audit of the current role model and permissions
• Designing an optimal scheme (roles: content manager, order manager, administrator)
• Configuring groups and module permissions
• Restricting access to pages
• Documentation (permission scheme and instructions for administrators)
• Training for staff (1–2 hours)
• 1-month warranty support

Timeframes

Setup for 2–3 groups with standard roles: 2 to 4 hours. A complex model with custom restrictions: up to 1 business day. Exact time determined after the audit. Administration time savings after implementation are 30–50%.

Get a consultation from a certified specialist—we will evaluate your project and propose the optimal solution. Contact us to order an access rights audit.