Developing a Corporate Portal on Bitrix24
As a company grows to 100 employees, chaos begins: vacation requests go into the manager's DMs, contracts are approved by passing files around with "ok" appended, a new employee waits a week to get access because the request got lost between IT and HR. A corporate portal on Bitrix24 brings all of this into one place—but real value appears not out of the box, but after customization for the specific organization's processes.
Organizational Structure and Employee Directory
The organizational structure is the foundation of the portal. In Bitrix24 it's built on a hierarchy of departments with unlimited nesting. Each employee is tied to a department, has a manager, and a set of rights determined by role.
What proper structure provides:
- Department heads automatically gain rights over their subordinates' tasks and reports
- Business processes route through org structure—a request goes to the direct manager, not a specific person
- An org chart is generated automatically and reflects reporting relationships in real-time
An employee card contains contacts, job title, photo. Through custom fields (UF_*) you add skills, projects, certifications, start date—everything HR and colleagues need.
Active Directory integration. For companies where employees exist in AD, synchronization eliminates duplicate database maintenance. Add an employee to AD—they automatically appear on the portal with the correct department. Fire them—they're blocked. Supports LDAP and AD via the standard ldap module.
Extranet users are a separate story. External contractors, vendors, freelancers get limited access: they see only the groups and tasks they've been explicitly invited to. The main structure and internal documents are hidden from them.
Business Process Automation—The Portal's Core
Business processes (BP) in Bitrix24 are a visual constructor working on BPMN principles. A process is built from blocks: actions, conditions, loops, parallel branches. This is why the portal is implemented—to replace paper forms, verbal approvals, and emails with subject line "RE: RE: FWD: Contract v3 FINAL (2)".
HR Processes
| Process | Participants | What Gets Automated |
|---|---|---|
| Vacation request | Employee -> Manager -> HR | Balance check, accounting notification, schedule update |
| Business trip | Employee -> Manager -> Finance | Per diem calculation, booking, expense report |
| Employee onboarding | HR -> IT -> Admin -> Manager | Account creation, equipment order, mentor assignment |
| Employee offboarding | HR -> IT -> Accounting -> Manager | Access revocation, handoff, final payout |
| Training request | Employee -> Manager -> HR -> Finance | Budget approval, certificate added to employee card |
Take employee onboarding—a process that without automation takes 3–5 days and regularly stalls. HR fills a form: name, title, department, start date. The BP launches:
- IT gets a task: create account, set up workstation, grant access to needed systems
- Admin gets a task: prepare workspace—desk, chair, access badge
- Manager gets a task: assign a mentor and prepare onboarding plan
- Each stage has a deadline. If IT doesn't create the account in 2 business days—escalate to IT manager
All tasks launch in parallel; the BP waits for all branches to complete, then HR gets a notification: "Workspace is ready." No phone calls, no "so what's the status on those access credentials?"
Each process is created in the BP designer. For lists—via "Lists -> Business Processes." For complex scenarios—via smart processes in CRM or activity blocks with PHP code that calls the platform API and external services.
Document Approval
A separate major topic. A contract is uploaded to Bitrix24.Disk and a BP launches:
- Sequential stages — legal, then CFO, then CEO
- Parallel — legal and finance simultaneously
- Voting — majority, unanimous, or first responder
- Delegation — approver is on vacation, automatically transfers to their deputy
- Escalation — exceeding the approval deadline notifies the superior
- Conditional routes — contract under 100K rubles goes to department head, over—to CFO
The full history is stored in the document card: who approved, when, with which comments, were there revisions.
Document Flow: Bitrix24.Disk
File storage with versioning. Documents are tied to tasks, CRM deals, project groups. Collaborative editing—via embedded OnlyOffice or Google Docs (via integration).
Access control is at the folder level. Sales see their documents, accounting sees theirs. Shared folders—for regulations and templates. Rights are inherited from the department structure.
For companies with strict document flow (ISO, internal audit), mandatory versioning is configured: each document change is recorded, rollback to previous version—two clicks. Disk integrates with the Bitrix24 desktop app—folders sync to your computer, file work like standard Windows/macOS folders.
Tasks and Projects
Task module: kanban boards, Gantt chart, checklists, dependencies, recurring tasks. Project groups combine tasks, files, and discussions in an isolated space.
For a corporate portal, integration with CRM is key: manager runs a deal -> assigns production task -> production reports -> manager closes deal. The whole chain is transparent; management sees bottlenecks in real time.
Project templates—for recurring processes. New product launch, event organization, entering new market—create a template with tasks, owners, deadlines. New project spins up in one click.
Telephony
Integration via SIP connector (connecting existing PBX) or Bitrix24's cloud PBX. Calls are recorded and tied to the customer card in CRM. Manager sees communication history; management sees call stats.
For large companies with existing infrastructure (Asterisk, FreePBX), SIP connector is the main option. A trunk is configured between your PBX and Bitrix24; call routing stays on your PBX side. Bitrix24 records the fact of the call and its recording.
Knowledge Base
The standard knowledge base in Bitrix24 works at the project group level. Articles are created in a visual editor, support nested sections, full-text search. For a proper wiki with versioning, cross-links, and article-level access rights—customization or an embedded app is needed.
Minimum startup set: company regulations, portal instructions, FAQ for new hires, document templates. A knowledge base reduces the load on HR and IT: instead of answering the same questions—link to an article.
Customization and Integrations
Standard functionality covers 60–70% of typical medium-company needs. The rest—custom solutions.
REST API — the primary tool for cloud Bitrix24. Work with CRM, tasks, users, lists, disk, business processes. Webhooks—for real-time data exchange with external systems.
Embedded apps — frame apps on any stack (React, Vue, vanilla JS) inside Bitrix24's interface. Access to JS SDK and REST API, displayed as tabs in CRM, tasks, in the left menu. Classic example—a KPI dashboard from multiple sources that can't be built with standard tools.
Smart processes — custom CRM entities with their own stages, fields, robots, and BPs. For processes that don't fit standard leads/deals: tenders, complaints, internal purchase requests.
Robots and triggers — custom automation. A robot calls an external API, sends data to 1C, creates documents in Google Workspace, notifies Telegram. A trigger fires a robot when an event occurs—new lead, stage change, task overdue.
Implementation Stages
| Stage | Content | Duration |
|---|---|---|
| Process Audit | Interviews with departments, map current processes, identify automation points | 1–2 weeks |
| Design | Portal architecture, BP structure, integration specs, prototypes | 1–2 weeks |
| Basic Module Setup | Structure, CRM, tasks, disk, telephony, knowledge base | 1–2 weeks |
| BP and Integration Development | Custom processes, REST connectors, embedded apps | 2–6 weeks |
| Data Migration | Transfer contacts, documents, history from legacy systems | 1–2 weeks |
| Training and Pilot Launch | Documentation, key user training, launch on one department | 1 week |
| Scaling | Connect remaining departments, iterate on feedback | 1–2 weeks |
Total timeline for a 100–300 employee company with 5–10 automated processes—2–3 months. For 50 employees with basic needs—3–4 weeks. For a holding with branches and complex structure—4+ months.
In parallel with deployment, an internal team of portal administrators emerges—employees who independently create business processes, manage structure, support users. Without such a team, the portal eventually becomes "just another chat app" where tasks exist but nobody uses automation.
Common Implementation Mistakes
Trying to automate everything at once. Company wants 30 business processes at launch. Result: none work properly, users are disappointed. Right approach—3–5 most painful processes first, rest added iteratively.
Ignoring training. Portal is configured, employees don't know how to request vacation. In a month, back to paper. One hour of training per department and clear instructions in the knowledge base—mandatory minimum.
Digitizing chaos. If the contract approval process wasn't documented on paper, it's impossible to automate. Process audit before implementation—not bureaucracy, but necessity. First document "how it works now," then design "how it should work," only then implement in BP.