Configure Document Approval in Bitrix24 Business Processes

Documents are uploaded to Disk, messaged to the manager, forwarded to the lawyer, who sends edits via email. The approval chain gets lost, document versions are confused—familiar? Bitrix24 business processes replace this unstructured correspondence with a formalized route. We, a team of engineers with 10+ years in Bitrix (over 50 approval implementations), set up a process that reduces document approval time by 3x compared to manual exchange. Guarantee: 6 months of free support after setup.

How the approval process works

Approval in Bitrix24 is implemented via the 'Assignment to User' action (CBPUserTypeActivity) in the business process designer (see Bitrix24 documentation). This is the key element: the process pauses, the approver receives a notification in the work feed with action buttons (Approve / Reject / Revise). The full history is stored: who approved, when, with what comments. Data is written to b_bizproc_workflow_log and b_bizproc_task.

Why business processes are better than manual approval?

Manual approval via email and chats leads to losses: up to 30% of contracts get lost, average approval time is 5–7 days. Bitrix24 business processes provide transparency: every step is logged, approval time is reduced to 1–2 days. Additionally, deadlines are automatically tracked and reminders are sent.

What approval routes can be configured?

Sequential approval — one after another. Lawyer → CFO → CEO. Each next person receives the task only after the previous one finishes. Implementation: three 'Assignment to User' blocks in sequence with conditions after each. If someone rejects, the 'Rejected' branch notifies the initiator.

Parallel approval — all at once. All approvers receive tasks simultaneously, the process waits for all responses. Used for formal signatures where order doesn't matter. Implementation: a 'Parallel Actions' block with a 'Assignment to User' in each branch.

Conditional approval — the route depends on document parameters. For example, a contract up to a certain threshold requires only department head; above that, the CFO is added; for even higher values, the CEO too.

Comparison of route types

Voting types

In the 'Assignment to User' block, voting type can be set:

• Unanimous — all must approve.
• Majority — >50% 'for' votes sufficient.
• First voter — as soon as one clicks, result is fixed.

This affects behavior in parallel approval: with 'majority', the process does not wait for all approvers' responses.

Integration with Disk documents

Files for approval are uploaded to the disk module. The business process is attached to a folder or file: Disk → [Folder] → Settings → Business Processes. When the BP is launched for a file, the task displays a link to the file with preview. Comments on approval are attached to the file's history.

File versioning during approval: uploading a new version via Disk → [File] → Upload new version creates a new version without losing the old one. Version history is linked to records in b_disk_version.

Notifications and reminders

The approver receives a notification in the Bitrix24 activity stream and via email (if notification rules are set). Reminders for unanswered tasks are implemented via a 'Wait' block with repeated notification. Standard scheme: wait 24 hours → send reminder → wait 24 hours → escalate to higher manager.

What is included in the business process setup?

We provide a full cycle of work:

1. Route design according to your organizational structure.
2. Configuration of all BP blocks, voting types, conditions.
3. Integration with Disk and attachment to documents.
4. Setting up notifications, reminders, and escalations.
5. Testing the process on real documents.
6. Documentation and administrator training (2–3 hours).

After setup, you receive a ready-to-use process with a 6-month free support guarantee. For example, for a manufacturing client, we configured a conditional approval process that cut the average approval time from 4 days to 1.5 days, reducing email overload by 70%. Get a consultation — discuss your scenario.

Setup timelines

A typical contract approval process with three levels of approval takes 1 business day including documentation and admin training. Contact us to discuss your scenario — we will estimate the project and offer an optimal solution.

How Choosing the Wrong 1C-Bitrix Edition Breaks Your Project

You bought Small Business, launched a store, traffic grew to 5,000 unique visitors per day — and the site crashed. Composite cache is only available in Business, web cluster too. An upgrade costs the difference in license price plus work to configure new modules. Choosing and configuring the right 1C-Bitrix edition upfront saves up to 40% on licensing. It also avoids unplanned upgrade costs — saving on average 15,000–30,000 RUB when upgrading from Small Business to Business in advance instead of urgently. Over 8 years of working with Bitrix, we have performed over 200 upgrades and seen all typical mistakes: from buying Start for a 50,000-product catalog to using Business for a landing page with 100 visits per day. Our principle is to select the edition that matches your real needs and configure it so you do not overpay for unnecessary modules — and also do not hit a ceiling at the first traffic spike.

1C-Bitrix Editions: Site Management

Four editions, and the difference lies not in the number of features but in the available core modules. The official 1C-Bitrix documentation states that composite cache is only available in Business and above.

Start is minimal, only content modules: iblock, form, basic SEO. For business card sites and landing pages. No sale module — cannot build a store.

Standard adds communication: blog, social network, forum, extended tech support. For corporate sites and portals with user-generated content.

Small Business is the first edition with e-commerce: the sale module appears. Comfortable ceiling is up to about 10,000 products without serious optimization. For small stores and catalogs with ordering.

Business is the full set: composite cache (TTFB drops from 800 ms to 50–80 ms — 10–15 times faster), web cluster, multisite, multi-warehouse, REST API. For large stores, marketplaces, projects with 10,000+ visitors per day.

How Does Composite Cache Reduce Server Load?

Composite cache (main.composite) speeds up page loading 10–15 times compared to dynamic generation. For a store with 3,000+ visitors per day, without composite the server starts struggling: average response time increases, database overload, checkout pages time out. Composite solves this radically — HTML is served by nginx without running PHP. It is important to correctly configure exclude masks for cart, personal account, and pages requiring real-time data. We configure this on every upgrade to Business.

1C-Bitrix official documentation: "Composite cache is available only in Business edition and higher."

Avoiding Common Mistakes in Edition Selection

Typical Mistakes

• Buying Start for an online store — no sale module, you either need to upgrade immediately or hack a custom ordering system.
• Choosing Small Business for a project that will grow to 10,000 products in six months — composite cache cannot be enabled, upgrading to Business costs the license difference plus configuration work.
• Using Business for a landing page — overpaying for features that will never be used.

Choosing an Edition for an Online Store

Hard Criteria for Edition Selection

By modules:

• 1C exchange (catalog) → at least Small Business
• Composite cache (main.composite) → only Business
• Web cluster (cluster) → only Business
• Multisite → only Business
• REST API → only Business

By load:

• Up to 1,000 unique visitors/day — any edition can handle
• 1,000–10,000 unique visitors/day — Small Business with nginx/php-fpm tuning hits a ceiling. Business with composite cache is the right choice
• 10,000+ unique visitors/day — only Business with composite and cluster

By budget:

• The price difference between editions is 2-5x
• Upgrade at any time — pay the difference in license cost
• Our principle: take the minimum sufficient. But if you know you will need composite in six months, get Business immediately, because an upgrade also involves configuration work. The total upgrade cost (license difference + setup) typically ranges from 10,000 to 50,000 RUB.

What Happens If You Ignore License Renewal?

An active license provides updates — new versions, security patches, bug fixes, marketplace access, and vendor tech support. When it expires, the site continues to work but remains without updates. For stores this is dangerous — security patches fix vulnerabilities in sale, catalog, main modules. Data leaks from b_sale_order or b_user are just a matter of time. Renewal costs a fraction of buying a new license — typically 20–30% of the full price. Regular renewal is insurance against unpatched CVEs.

Cost Benefits of Planned Edition Upgrades

1C-Bitrix allows upgrading without reinstallation — data is preserved. Process:

1. Pay the difference in license cost
2. Activate new key: Settings → Updates → Registration
3. Install newly available modules via admin panel
4. Configure new functionality
5. Test compatibility

What we do during an upgrade:

• Check custom code for conflicts with new modules — especially custom event handlers like OnBeforeOrderAdd, OnSaleBasketSaved
• Enable and configure composite cache — correct exclude masks for dynamic pages (cart, checkout, personal account)
• Configure multi-warehouse if needed — b_catalog_store, warehouse selection rules
• Run full functional testing on staging
• Document changes

As a result, you get:

• A working site on the new edition with no data loss
• Configured composite cache (if upgraded to Business)
• Testing report and recommendations for further optimization
• Access to staging and documentation of changes

Integrating Site Management with Bitrix24

A common scenario: site on 1C-Bitrix + CRM in Bitrix24. Orders from b_sale_order automatically become leads or deals, unified authorization, client base synchronization. Site forms (form or custom) feed into the CRM funnel. These are two separate licenses and two separate products — integration between them is standard and stable.

Practical Recommendations

• Do not skimp on the edition if you know the functionality will be needed in six months. Upgrading costs the same difference plus configuration and testing.
• Business for projects with growth ambitions — composite cache pays for the price difference at the first traffic spike. Without composite, 3,000+ unique visitors/day will strain the server.
• Bitrix24 and Site Management are different products with different licenses. Confusion here costs money.
• Renew your license annually — renewal is much cheaper than buying a new one, and without updates you risk unpatched CVEs.

What We Offer: Turnkey Selection and Configuration

We do not just consult — we handle the full cycle: analyze your current project, select the edition, purchase the license (if needed), migrate, configure all modules, and train your team. As part of the service, you get:

• An edition selection report with justification
• Migration plan (if upgrading)
• Fully set up staging with the new edition
• Composite cache and cluster configuration (if necessary)
• Documentation of the new configuration
• Guarantee of site functionality after the transition

Contact us today — we can assess your project within one business day and propose the optimal configuration. Receive a personalized cost estimate for selecting and configuring your 1C-Bitrix edition right now.