Setting up Bitrix24 Wiki

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.

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1262
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    851
  • 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
    585
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    751
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    657
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    989

Configuration of Bitrix24 Wiki

The client work process is documented in Google Docs. CRM instructions are in Notion. Email templates are in a Drive folder. A new employee spends the first week searching for documents and gets three different answers to one question. Wiki in B24 solves the problem: everything in one place with structured pages, search, access rights, and versioning.

What is Wiki in B24

Wiki is a built-in B24 module for creating internal pages with formatted text, tables, images, and links. It works on the Wikipedia principle: each page has a unique URL, change history, and can link to other pages. The module is available in Services → Wiki (on plans with the "Company" tool).

Difference from Knowledge Base: Wiki is a free structure of pages with cross-references. Knowledge Base is articles organized by categories and hierarchy. Wiki is suitable for reference information that is frequently updated and interconnected.

Page Structure

Before creating pages, you need a structure. Typical hierarchy:

  • Wiki Home Page — table of contents with links to sections
    • Sales Department — procedures, scripts, CRM work
    • Support — request handling algorithms, FAQ
    • HR — onboarding, vacations, policies
    • Development — code standards, deployment, infrastructure
    • General — company details, contacts, organizational structure

Each section is a separate page with subpages. Navigation is through links on the home page and through internal search.

Page Templates

For standard pages (instructions, procedures, process descriptions), templates are created. A template defines structure: headings, required sections, format. This ensures consistency — all instructions look the same, information is easy to find.

Example "Instruction" template:

  • Process name
  • When to apply
  • Step-by-step actions
  • Person responsible
  • Related documents

Access Rights

Wiki supports access configuration at section level:

  • Read — all employees see the page
  • Edit — only certain roles or departments
  • Create — who can add new pages to a section

Typical scheme: everyone reads, department heads edit their sections, admin manages structure.

Search and Navigation

B24 built-in search indexes Wiki page content. To improve search quality:

  • Use keywords in page titles
  • Add tags to pages
  • Create cross-references between related pages
  • Maintain an up-to-date table of contents on the home page

Migration from External Systems

If documentation is maintained in Confluence, Notion, or Google Docs — transfer content to B24 Wiki. Process: export from source (HTML/Markdown), adapt formatting, create pages via interface or REST API (wiki.page.add), verify links and images.

What We Configure

  • Wiki section structure for company departments
  • Page templates for standard documents
  • Access rights: read/edit by departments
  • Table of contents and navigation with links
  • Content migration from external systems (Confluence, Notion, Google Docs)
  • Editor training: creating and updating pages