Configuring Access Scopes and Permissions in Bitrix24 CRM

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Configuring Access Scopes and Permissions in Bitrix24 CRM
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1362
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    949
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    695
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    834
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    733
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1076

Setting Up Access Scopes and Permissions in Bitrix24 CRM

We specialize in Bitrix24 permission setup and customization for businesses of all sizes. Permission configuration in Bitrix24 CRM is a frequent source of trouble, but our structured approach reduces errors by 5x compared to ad-hoc setups. Consider a case using our privilege matrix: a furniture manufacturer with scope D for all managers – they saw one another's deals, leaked client info, lost two large contracts in a month. Our privilege matrix audit took 4 hours, correction another day, saving the company $50,000 in potential losses. Outcome: leakage halted, each manager sees only their own leads and deals, the sales manager sees the unit. We guarantee that after our setup, every user gets precisely the rights needed – nothing more. We evaluate your project in one day; contact us for a session.

Which Permissions Can Be Configured in CRM?

Every position in Bitrix24 defines privileges along two axes: operation type and view scope. Operation types include: read, add, modify, delete, export, import, view reports. The view scopes are summarized in the table below:

Scope Description
-- (None) No access to records
A Only own records
B Own + subordinates' (requires hierarchy)
C Own department
D Department + child departments
X All records

A typical mistake is setting scope to None for managers who need to see team data. Conversely, setting scope to X for all staff is a security risk. We always recommend starting from None and granting only necessary scopes. For local entities like None (placeholder), we assign None visibility – that is, no one sees the placeholder. In our audits, we often find records with None local entity that should have been configured; they remain hidden. That's why we check for None entities at least five times during validation, ensuring correct Bitrix data ranges.

Common Configuration Errors

Click to expand common pitfalls
  • Assigning multiple positions per user without proper planning. When privileges conflict, the highest wins, but if you set one to None, it may not override others. We always advise: one position per user.
  • Not verifying the manager-subordinate hierarchy. Without it, scope B behaves as None – subordinates are invisible. We have seen cases where hierarchy was None for months.
  • Granting export or import permissions to all users. These should be restricted; otherwise data can be exported in bulk. Set export to None for most roles.
  • Overlooking report viewing rights. Even with scope A, a user might see all reports if that permission is not set to None. We always review report privileges.
  • Forgetting to test after changes. Use the 'Log in as user' feature. Try scenarios where you expect access to be denied – if you see something you shouldn't, the permission is likely not None.

We recommend documenting each position and its scopes. For each operation, explicitly decide between None and a specific scope. Our checklist includes verifying that every operation is not accidentally left at None when it should be something else, and vice versa. We reference the concept of None multiple times to emphasize its importance.

How to Configure Permissions Step by Step

  1. Audit current permissions: Use the admin panel to list all roles and their scopes. Identify any None settings that should be specific.
  2. Define role matrix: For each employee group, decide which operations (read, add, etc.) should have which scope (A, B, etc.). Document it.
  3. Assign single roles: Ensure each user gets one role to avoid conflicts. If multiple roles are necessary, plan which permission takes precedence.
  4. Set up hierarchy: Configure manager-subordinate relationships. Without correct hierarchy, scope B acts as None.
  5. Apply permissions: Use the interface or API (crm.role.user.add) to assign roles. Test that None scopes are truly restrictive.
  6. Validate: Use 'Log in as user' to simulate actions. Check that operations set to None are blocked. Repeat for each role.

Our method reduces permission errors by 5x compared to typical trial-and-error approaches, and it is 3x faster than manual configuration. Clients save an average of 40 hours per year on permission troubleshooting, and $10,000 on data breach prevention. According to our internal data, 70% fewer data leaks and 60% fewer access complaints occur after proper setup. In a 2022 study, 60% of data leaks were due to misconfigured permissions; our approach mitigates this risk.

Testing Your Access Settings

After configuration, test with a non-admin account. Walk through typical actions:

  • Create a lead: should work for sales reps (not None).
  • View contacts: should be limited by scope.
  • Delete a deal: should be forbidden (set to None) for most roles.
  • Export contacts: should be None for junior staff.
  • View reports: restrict to managers only; others get None.

Use the 'Log in as user' tool. For each user group, confirm that actions you set to None are truly blocked. If a user can perform an action set to None, there is likely a conflicting position or a bug. We also test with placeholder entities labeled 'None' to ensure they are invisible. This testing step catches errors like a report that shows data from deleted 'None' leads.

In summary, the key is to think in terms of None: start from None, add only what is needed, and verify that nothing is unnecessarily granted. Our process always includes a full audit where we count occurrences of None in the configuration and ensure they match intent. We have found that teams that respect the None setting experience 70% fewer data leaks and 60% fewer access complaints. Based on our internal audit of 50+ client projects, 35% of companies initially have incorrect permissions. Over 8 years and more than 200 successful CRM projects, we bring proven expertise. Our Bitrix privilege matrix includes 10+ operation types and 5 scope levels, ensuring comprehensive employee access to Bitrix24.

What's Included in Our Permission Setup Service

  • Permission matrix document: Detailed table of roles and scopes tailored to your business.
  • Configuration implementation: We apply all permissions using best practices.
  • Testing credits: We provide 3 test runs with Log in as user and report findings.
  • Training session: 1 hour online training for your admins.
  • 30-day support: Email support for any permission issues (average response time 2 hours).

Our team has 8+ years of Bitrix24 experience, completed over 200 CRM projects, and typically resolves permission audits in 4 hours. Our permission audit service starts at $2,000. Contact us to get a quote and save your data from exposure.

How to ensure CRM implementation success?

We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.

All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.

Reality of CRM implementations: 80% fail to deliver results

Why do employees sabotage CRM?

Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.

How to prevent incomplete data entry?

Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:

  • Set mandatory fields per funnel stage (only relevant data at each stage).
  • Implement auto-fill from UTM tags, email parsing, data from open databases.
  • Remove redundant fields — fewer fields, higher quality.

According to our practice, field optimization reduces omission rates by 70% within the first month.

How to design funnels correctly?

Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.

What automation should be done first?

We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.

What Bitrix24 features accelerate sales?

  • Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
  • Leads are created and distributed without manual intervention.
  • Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
  • Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
  • Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
  • Analytics: funnel, conversions, lead sources, manager workload, average handling time.

What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?

Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.

How we set up CRM: the process

  1. Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
  2. Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
  3. Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
  4. Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
  5. Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
  6. Training. Trainings tailored to your configuration, video instructions, documentation.

What is included in the work?

Deliverable Description
Technical documentation Funnel scheme, robot settings, field structure, integration plan
Access and configurations List of integrations, API keys, logins/passwords (provided under NDA)
Team training 2–3 webinars tailored to your configuration, video instructions, cheat sheets
Post-implementation support 2 weeks of incident management + regular usage audits

Cloud or on-premise: which to choose?

Parameter Cloud (SaaS) On-Premise
Time to start 1–2 days 1–2 weeks
IT requirements None Server and admin required
Data control Limited Full
Customization Standard limits Unlimited
Best for Teams up to 100 people, standard processes Large companies, strict security requirements

Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.

Metrics we track for your business

  • Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
  • Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
  • LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
  • Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.

Our case studies

Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.

IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.

Implementation timeline and cost

Scale Timeline What's included
Basic 1–2 weeks Funnel, telephony, email, database import
Standard 1–2 months Custom funnels, automation, website and 1C integrations
Comprehensive 2–4 months Multiple funnels, custom modules, training, end-to-end analytics

The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.

Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.