1C-Bitrix Admin Panel Configuration
The standard Bitrix admin panel after installation is configured "for everyone"—the administrator sees all modules, the news editor sees the same menu items as the system administrator. This creates confusion and risks accidentally changing critical settings. Proper panel setup means access control, desktop configuration, and disabling unnecessary items.
Roles and Admin Panel Access Rights
In Bitrix, admin interface rights are set via user groups and module rights. Each module defines its access levels. Configuration: Settings → User Groups → [Group] → Module Rights.
Typical configuration for content editor: access to iblock module (infoblocks)—"Editor" level, to main module—profile only, to sale module—no access. Editor logs into /bitrix/admin/ and sees only "Content" section with infoblocks—nothing extra.
Subtlety: infoblock rights are configured separately from module rights. In each infoblock settings (/bitrix/admin/iblock_edit.php)—"Access Rights" tab. Even if group has iblock module access, specific infoblock can be closed from editing.
Administrator Desktop
Desktop (/bitrix/admin/index.php) configured individually per user. Standard widgets: visit statistics, recent orders, system events, tasks. Remove unnecessary, add useful. For store manager—"New Orders" and "Warehouse Inventory" widgets. For SEO specialist—search statistics.
Front-end Admin Panel Configuration
On the frontend, authorized administrators see the administrative panel (toolbar) with edit buttons. Its behavior configured in Settings → Main Module → Panel Settings:
- Which groups see panel on frontend
- Display mode (horizontal / hidden)
- Panel buttons (edit page, go to admin, clear cache)
On production site, important: panel should be visible only to authorized staff, not anonymous users. Obvious, but sometimes "All Users" group accidentally gets access.
Admin Panel Menu Configuration
Menu items in /bitrix/admin/ controlled via module menu files. Custom items added to local/php_interface/include/admin_menu_custom.php—without core edits. Unused sections hidden via module access rights, not by menu deletion.
Admin panel configuration for specific roles and company workflows: 1-3 days.