Configuring the 1C-Bitrix admin panel is a task that arises after every clean installation. The default panel contains dozens of unused modules, and access to core settings is often open to all users. A content manager could accidentally change critical parameters; developers waste time navigating irrelevant menu items. Without proper access control and disabling unnecessary functionality, the admin panel slows down and becomes insecure. We solve these problems in 2–4 hours: we tailor the environment precisely to your business processes.
Case in point: an e-commerce store with 50,000 SKUs, 1C UT integration, and two manager groups (procurement and sales). The default interface showed procurement managers inaccessible sections and loaded social network modules. After implementing role-based access and a custom menu, task speed increased threefold. Managers saved 2 hours per day, leading to significant cost savings.
Improper configuration can lead to serious downtime and financial losses. Our setup pays for itself quickly.
What is included in admin panel configuration
- Audit of current configuration: permissions, modules, prologs.
- Access control: groups, roles, section access.
- Menu customization: hide/add items, sorting.
- Security settings: IP filtering, CAPTCHA, two-factor authentication, HTTPS.
- 1C integration via CommerceML: exchange of orders and reference books.
- Documentation, team training, 60-day support.
Every project starts with an audit. We check b_option, module settings, prologs, and epilogs. Then we design an access control scheme: groups with different access levels, hiding menu items via OnBuildGlobalMenu, security configuration. The cost is fixed in the contract and depends on the number of groups and modules. We provide a 60-day guarantee.
Why does the Bitrix admin panel slow down and how to fix it?
The main reason is open modules and excessive requests. For example, the "Social Network" module loads js/css even when not used. We disable unused modules, configure tagged caching, and script aggregation. This speeds up loading by 2-3 times. Our configuration is faster than the default—benchmarks on UAT environment confirm this.
Structure of the admin panel
The admin panel (/bitrix/admin/) consists of several layers:
- Main menu — formed based on installed modules and the
OnBuildGlobalMenuevent. - Context menu — depends on permissions and current page.
- Workspace — module pages, infoblocks, HL-blocks.
- Notification panel — tasks, updates, integrations.
The entry point is /bitrix/modules/main/admin_menu.php. The menu is built via events, which we customize in /local/php_interface/init.php.
How to configure the menu and prologs?
For customization, we use files:
-
/bitrix/php_interface/dbconn.php— database parameters. -
/local/php_interface/init.php— event handlers.
Example of adding a custom menu item:
AddEventHandler('main', 'OnBuildGlobalMenu', function(&$globalMenu, &$moduleMenu) { $moduleMenu[] = [ 'parent_menu' => 'global_menu_content', 'sort' => 100, 'text' => 'Order Analytics', 'url' => 'analytics_page.php', 'more_url' => ['analytics_page.php'], ]; }); Details on the event are in the 1C-Bitrix documentation.
Admin panel security
Recommendations on role-based access control are described on Wikipedia. We apply:
| Setting | Location | Recommendation |
|---|---|---|
| IP restriction | b_option of main module |
List of corporate IPs |
| CAPTCHA on login | Main module settings | Enable |
| Two-factor authentication | Security module | Google Authenticator |
| HTTPS for admin | nginx/.htaccess | 301 redirect |
| Change admin URL | nginx routing | /admin-hidden-path/ |
Recommendations on HTTPS setup can be found in this Wikipedia article.
Additional security measures
- Auditing file configuration permissions (
dbconn.php,.settings.php). - Disabling debug mode (
BX_DEBUG=false). - Using a Web Application Firewall at the nginx level.
How we work: stages and timelines
- Analysis (1 hour): audit of permissions, modules, load. Identify bottlenecks.
- Design (2 hours): access control scheme, menu draft, caching list.
- Implementation (2–6 hours): prolog configuration, events, permissions, security, 1C integration.
- Testing (1 hour): verification on UAT environment, regression.
- Deployment and documentation (2 hours): release to production, configuration description.
Timelines — from 2 hours to 2 days. Cost is individual, depending on complexity. Get a consultation: we'll estimate more precisely.
Common configuration mistakes
| Mistake | Consequence | Solution |
|---|---|---|
Direct editing /bitrix/admin_menu.php |
Breaks on update | Use events |
Open access to /bitrix/ without HTTPS |
Session hijacking | HTTPS and redirect |
| Storing passwords in plain text | Compromise | Use OTP |
| Forgetting to disable "System Log" module in production | Load increase | Disable unused modules |
| Lack of documentation | Maintenance complexity | We document everything |
We guarantee our configuration for 60 days. If something breaks after our intervention — we fix it free of charge. Order your 1C-Bitrix admin panel configuration and get a tool that works for your business. Contact us for a consultation and cost estimate for your project.