Developing Custom Admin Pages in 1C-Bitrix

We often encounter scenarios where the standard admin section of 1C-Bitrix doesn't cover specific business processes. Manual stock synchronization from an external system, bulk price updates via formula, integration settings management — these require custom admin pages. Developing directly in /bitrix/admin/ is not advisable — platform updates will overwrite changes. The correct path is /local/. Over 5+ years, we have developed more than 50 custom admin interfaces for Bitrix, from simple forms to multi-page analytics dashboards. This article covers the technical details of creating such pages. Custom admin pages allow implementing any functionality not available in the standard package.

How to Place and Structure Custom Admin Pages?

Placement in /local/admin/ — Developing Custom Admin Pages

Place custom page files in /local/admin/. Bitrix automatically includes this path when searching for admin pages. The page becomes accessible at /bitrix/admin/my_page.php if the file is at /local/admin/my_page.php. Alternatively, create the page as a component in /local/components/ and include it via a wrapper. This is the preferred approach for complex interfaces.

Structure of a Minimal Admin Page

<?php // /local/admin/my_custom_page.php require_once($_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_admin_before.php'); // Check permissions $APPLICATION->SetTitle('My Page'); if (!$USER->IsAdmin() && !$USER->CanDoOperation('edit_php')) { $APPLICATION->AuthForm('Access denied'); } require_once($_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_admin_after.php'); // Page content ?> <div class="adm-content-wrap"> <!-- Interface HTML --> </div> <?php require_once($_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/epilog_admin.php'); 

Three required includes form the correct wrapper: header, navigation, and footer of the admin section. Without them, the page will open without styling.

Using Bitrix Admin Helpers

Bitrix provides a set of classes for building standard admin UI elements. Using these classes gives a native look and saves layout effort. Consider CAdminList and CAdminForm.

use Bitrix\Main\UI\Filter\Options as FilterOptions; // CAdminList — table with sorting, pagination, and filter $oList = new CAdminList('my_list_id'); $lAdmin->AddHeaders([ ['id' => 'ID', 'content' => 'ID', 'sort' => 'ID'], ['id' => 'NAME', 'content' => 'Name', 'sort' => 'NAME'], ['id' => 'DATE', 'content' => 'Date'], ]); while ($row = $rsData->Fetch()) { $oRow = &$oList->AddRow('ID_' . $row['ID'], $row); $oRow->AddActions([ ['TEXT' => 'Edit', 'ONCLICK' => "jsUtils.Redirect([], 'my_edit.php?ID=" . $row['ID'] . "')], ['TEXT' => 'Delete', 'ACTION' => $oList->ActionDoGroup($row['ID'], 'delete')], ]); } $oList->DisplayList(); // CAdminForm — edit form with tabs $oTabControl = new CAdminTabControl('tabControl', [ ['DIV' => 'tab1', 'TAB' => 'Main', 'ICON' => 'main_user_edit'], ['DIV' => 'tab2', 'TAB' => 'Additional'], ]); $oTabControl->Begin(); $oTabControl->BeginNextTab(); // first tab fields $oTabControl->BeginNextTab(); // second tab fields $oTabControl->Buttons(['btnSave' => true, 'btnApply' => true, 'btnCancel' => true]); $oTabControl->End(); 

How to Add a Page to the Menu and Set Up Permissions?

Adding to Menu

The page must be accessible from the menu, not just via direct URL. Register via event handler in /local/php_interface/init.php:

AddEventHandler('main', 'OnBuildGlobalMenu', function(&$globalMenu, &$moduleMenu) { $moduleMenu[] = [ 'parent_menu' => 'global_menu_services', 'sort' => 500, 'text' => 'Synchronization', 'title' => 'Manage synchronization with external system', 'url' => 'my_custom_page.php', 'icon' => 'main_menu_tasks', 'page_icon' => 'main_page_icon', 'more_url' => ['my_custom_page.php', 'my_custom_edit.php'], ]; }); 

The more_url parameter is needed to keep the menu item active when navigating to related pages.

Access Rights

Custom pages must check permissions themselves. Options:

• Check $USER->IsAdmin() — only for pages accessible exclusively to admins
• Check $USER->CanDoOperation('operation_name') — for granular control
• Check module right: CModule::IncludeModule('main') && $USER->GetRights('mymodule') >= 'W'

According to official 1C-Bitrix documentation, if a page should be accessible to a specific group, it's better to create a custom module with rights registration via RegisterModuleDependences.

Working with Data: D7 ORM vs Old API

For custom pages, we recommend using D7 ORM (\Bitrix\Main\ORM). If data is stored in custom tables, create an entity class:

namespace Local\MyModule; use Bitrix\Main\ORM\Data\DataManager; use Bitrix\Main\ORM\Fields; class MyEntityTable extends DataManager { public static function getTableName(): string { return 'my_custom_table'; } public static function getMap(): array { return [ new Fields\IntegerField('ID', ['primary' => true, 'autocomplete' => true]), new Fields\StringField('NAME', ['required' => true]), new Fields\DatetimeField('CREATED_AT'), ]; } } 

Then MyEntityTable::getList(), ::add(), ::update(), ::delete() work via the standard ORM.

How to Handle Forms and AJAX?

Bitrix admin pages traditionally use POST forms with CSRF token (bitrix_sessid_post()). For AJAX requests:

// Check session token if (!check_bitrix_sessid()) { die(json_encode(['error' => 'Invalid session'])); } // In JS (using BX.ajax) BX.ajax.runAction('local:my.action', { data: { param: value }, sessid: BX.bitrix_sessid() }); 

For modern AJAX interfaces, use \Bitrix\Main\Engine\Controller with routing via /.action.php — this is the D7 approach recommended for new developments.

Timeline and Scope

The work includes:

• Audit of current architecture and TOR approval
• Prototype development in /local/admin/ or /local/components/
• Logic implementation using D7 ORM
• Menu integration and access rights configuration
• Testing on staging and refinements
• Source code and documentation handover
• 30-day warranty support

Typical Tasks for Custom Pages

• Synchronization control panel with 1C or external APIs (manual trigger, operation log)
• Bulk product editing by non-standard criteria
• Analytics dashboard based on data from multiple modules
• Integration settings management (API keys, webhooks, field mapping)
• Content migration tools between environments

Why Choose Us?

Our team has 5+ years of Bitrix development experience and has completed over 50 projects customizing the admin panel. We guarantee compatibility with the latest platform versions, provide full documentation, and offer post-delivery support. Contact us for a consultation or order turnkey development — we will assess your project within one day. Save time on manual data processing and get transparent project cost — that's what you receive.

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