Creating an Administrator Guide for 1C-Bitrix
An administrator guide for a Bitrix project is not a retelling of the official 1C-Bitrix documentation. It describes the specific installation: which infoblocks exist and what can be edited in them, how the publication chain works, which settings must not be touched and why. Without such a document, each new administrator spends weeks onboarding, and half of the questions are resolved by calling the developer. Our experience shows: a well-written guide reduces onboarding time by 3–5 times and eliminates typical administration errors.
Problems We Solve
The main challenge: the guide becomes outdated with every update. The solution is a process where the developer updates the relevant section of the guide when delivering a task. For storage, use a system with version history—Confluence, Notion, or Google Docs. A Word file on the server is an anti-pattern because versioning is impossible. Do not place the guide in a Git repository: it contains operational information unrelated to code. In practice, cloud systems like Confluence handle freshness much better.
We guarantee the guide remains current thanks to our maintenance checklist. Our team’s certificates and licenses confirm competence in Bitrix.
What the Administrator Sections Should Contain
A typical guide composition:
| Section |
Content |
| Access and Environment |
Panel addresses, password manager link, description of roles and permission groups |
| Content Management |
Infoblocks, fields, screenshots, limitations |
| Catalog Management (e-commerce) |
Products, prices, warehouses (catalog), discounts (sale) |
| Orders and Customers |
Order statuses, lifecycle |
| Technical Procedures |
Backup, kernel update, cache clearing |
Infoblock Description: Template for Each
For each infoblock create a card using the template:
Infoblock: News
Type: news | ID: 3 | Symbolic code: news
Menu location: Content → News
Admin list URL: /bitrix/admin/iblock_list_admin.php?IBLOCK_ID=3&type=news
Element fields:
- Name (NAME) — required. News title
- Symbolic code (CODE) — generated automatically, do not edit
- Publication date (ACTIVE_FROM) — if not set, the news is published immediately
- Preview text (PREVIEW_TEXT) — short description for the list, up to 300 characters
- Preview image (PREVIEW_PICTURE) — 800×600 px, JPG/PNG, max 500 KB
- Detail text (DETAIL_TEXT) — TinyMCE editor, full news text
- Tags (TAGS) — comma-separated, used for filtering
What must not be done:
- Change the symbolic code of a published news item (breaks the URL and loses search positions)
- Delete sections with active elements without reassigning them
This format is understandable for people without a technical background and does not require explanations each time. In practice, administrators often need information about what restrictions exist when editing, to avoid breaking the site with an accidental action.
Description of Technical Procedures
Cache clearing — the most frequent administrator action. In /bitrix/admin/cache.php there are two options: clear all cache or only component cache. Describe what to clear for different situations. If the site uses HTML cache (/bitrix/html_pages/), it must be cleared separately. We recommend documenting that caching may hide new data for up to 24 hours if TTL is high, so for critical errors cache must be cleared immediately.
Backup — built-in module (/bitrix/admin/backup.php). Describe how to create a manual backup, where it is stored, how to restore the site. This step saves the day in critical moments. In practice, regular backups prevent data loss due to hardware failure, hacking, or accidental deletion of important information by an administrator.
Module updates — through the Marketplace or /bitrix/admin/update_system.php. Advice: do not update immediately after release — give time to detect bugs. After updating, check functionality against a list of pages. Document the rollback procedure in case of critical problems after the update.
Specifics for Multisite Installations
If multiple sites run on a single Bitrix kernel, the guide must clearly differentiate: which infoblocks are shared and which are site-specific. The b_iblock table contains the SITE_ID field. The administrator must understand that changing a shared infoblock affects all sites. A mistake here is costly: a change in one infoblock can silently break logic on other sites. We recommend marking shared infoblocks in the guide with yellow, site-specific with green, to visually highlight critical points.
What’s Included in the Work
We prepare a complete administrator guide:
- Structured documentation for all sections
- Screenshots and infoblock card templates
- Instructions for technical procedures (cache, backup, updates)
- Maintenance checklist to keep it up to date
- Administrator training session on working with the document
- Consultation support for one month after delivery
Process and Delivery
Work begins with a detailed interview with the current administrative and technical team. We determine the site maintenance schedule, content update frequency, and typical administrator errors. Based on that, we create a guide tailored to your specific installation. Then we conduct a training session with administrators and leave a contact for questions for one month. The documentation is stored on a secure cloud service with versioning and change history.
With over 5 years on the market and 50+ completed Bitrix projects, order a guide and get a document that will save your team time.
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.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
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?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.
