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.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.