Setting Up the Bitrix24 Mobile App
The Bitrix24 mobile app comes out-of-the-box with all plans, but without proper configuration, employees can waste up to 30% of their working time. They miss notifications about new deals, can't see calendar meetings, and fail to sync corporate email. This is especially acute in on-premise versions: you need to manually configure an SSL certificate, set up Firebase for Android, and APNs for iOS. We have been configuring the mobile app for over 10 years and have completed 50+ projects for both cloud and on-premise versions. During this time, we identified typical pain points and developed quick scripts to resolve them. The cost of the setup is determined individually after an audit—basic configuration starts at a few hours of work, while extended setup with integrations may take one to two days.
What Problems Does the Setup Solve?
Silent communication channels. Without push notifications, managers can lose up to 2 hours responding to a lead. Supervisors don't see task completions. Configuring Firebase and APNs resolves this in 30 minutes.
Incomplete CRM access. The mobile app may show other people's deals or hide necessary fields. Adjusting permissions and views takes about one hour.
Disjointed calendars. IMAP sync doesn't transfer meetings from Outlook. Switching to Exchange Web Services or OAuth2 for Google Workspace provides full two-way synchronization.
How to Set Up Push Notifications for On-Premise
Push notifications work through Firebase Cloud Messaging (Android) and Apple Push Notification Service (iOS). For on-premise Bitrix24, configuration is done in the admin section: Settings → Product Settings → Push and Pull. You need to:
- Create a project in Firebase Console and get a Server Key.
- For iOS, obtain an APNs certificate from your Apple Developer Account.
- Enter both keys into the
pullmodule settings.
We use ready-made scripts for quick Firebase and APNs integration, reducing setup time to 30 minutes. Result: notifications arrive within 3 seconds after a system event. In one project, this increased request processing speed by 25%.
Why Calendar Sync Matters
If email is configured via IMAP, corporate calendar events won't sync. Switching to Exchange Web Services or OAuth2 for Google Workspace solves the issue: after configuration, events appear in the mobile app on both ends. Comparison: Exchange setup is twice as fast as IMAP and supports full two-way sync without delays. In one case, this saved the sales department 10 hours per month on meeting coordination.
CRM in Mobile: Field and Permission Configuration
By default, the mobile app shows: leads, deals, contacts, companies, calls. To adjust field visibility, go to CRM → Settings → Fields and create separate mobile display profiles. For automatic contact card display on incoming calls, enable caller identification in telephony settings. The app shows the CRM contact card during an incoming call if the number is found in b_crm_contact_detail. In 95% of cases, this speeds up call handling by 30%. For custom fields, we use the REST API to add fields to the "Mobile App" view.
How to Configure Access Rights
In Settings → Company Structure → Roles, for mobile devices, it's important to: restrict CRM data export, prevent record deletion, and set Disk access to corporate storage only (not personal). This is critical for security policies. Our certified specialists perform permissions audits and provide recommendations. According to our data, 70% of companies discover excessive permissions after the first analysis.
What's Included in the Setup
| Component | Description |
|---|---|
| Current configuration audit | Check Bitrix24 version, SSL, modules |
| Push notifications | Firebase (Android) and APNs (iOS) configuration |
| CRM fields | Customize views for mobile devices |
| Calendar sync | Exchange Web Services or Google Workspace OAuth2 |
| Permissions | Role matrix with security audit |
| Documentation | Admin guide, checklist |
| Testing | Verify all scenarios on real devices |
Configuration Comparison
| Setup Component | Basic Configuration | Extended Configuration |
|---|---|---|
| SSL certificate and ports | Check and configure | Install Let's Encrypt |
| Push notifications | Firebase + APNs | Additional: custom sounds |
| CRM fields | Standard display | Individual field profiles |
| Email sync | IMAP | Exchange / Google Workspace |
| Access rights | Roles by department | Role matrix with audit |
Work Process
- Analysis — review current configuration, identify bottlenecks.
- Design — define push composition, permissions, sync lists.
- Setup — configure SSL, Firebase, APNs, roles, CRM fields.
- Testing — verify push, sync, accessibility of all sections.
- Delivery — provide instructions and lock down the result.
Typical Mistakes When Doing It Yourself
- Wrong Firebase Server Key — notifications don't work at all.
- Missing SSL certificate — app can't connect to on-premise server.
- Forgotten permissions — employees see personal data of others.
-
pullmodule not enabled — push doesn't work.
Pre-launch checklist:
- [ ] SSL certificate (for on-premise) installed and verified.
- [ ] Firebase Server Key added to
pullsettings. - [ ] APNs certificate uploaded.
- [ ]
calendarmodule enabled. - [ ] Mobile access roles configured.
- [ ] Test notification sent on Android and iOS.
Timeline and Pricing
Basic setup takes 2 to 4 hours. Extended setup with Exchange or Google Workspace integration takes 1-2 days. Pricing is determined individually based on complexity and Bitrix24 edition. We work with both cloud and on-premise versions. Contact us for a consultation — we'll discuss details and agree on timelines.
We guarantee stable operation of all components after setup. Order the configuration of your Bitrix24 mobile app — and keep your team always connected.