Frontend architecture and navigation

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment Release specific self hosted

Overview

The React interface is a single-page application. Its shared shell contains grouped navigation, global search, quick creation and session controls. Hash navigation selects modules and record details. Individual components implement commercial documents, reports, scheduling, automation and administration. Available navigation depends on effective permissions and enabled capabilities; hiding a menu is not the security enforcement mechanism.

Purpose

Use this article to understand page loading, navigation and client-side behavior when supporting a user or extending a compatible integration.

Prerequisites

• An authenticated browser session.

• The user role and module involved in the reported issue.

Procedure

1. Reproduce the problem from the normal sidebar or a record link, and record the visible page title and action. Avoid copying a URL containing a password recovery token.

2. Check whether the module is available for the user. Compare the effective module permissions and capability state with an administrator.

3. Use the page Refresh action after a permission, status or record change. The client briefly caches reads and invalidates its cache after writes.

4. For a validation failure, read the form-level message and the affected field. The API response supplies the authoritative rejection.

5. If a problem appears only at a narrow viewport, reproduce it at desktop width and report both viewport sizes and the affected control.

Expected result

A support report distinguishes unavailable navigation, stale client state, validation feedback and a reproducible layout problem.

Important notes

• The API client includes credentials and the CSRF header for authenticated operations. Browser storage should never be used to distribute service credentials.

• Record views and layout metadata customize presentation, but server-side permission and field checks remain authoritative.

• The sidebar places Pipelines in Sales, while the breadcrumb helper labels it Automation in this release. Use the visible Pipelines entry and record the labeling inconsistency.

Troubleshooting

• An operation fails after another user edits the record: refresh and reapply the intended change to the latest version.

• A deep link opens an unexpected screen: navigate through the sidebar and compare the release baseline before reporting a broken route.

Related articles

• Authorization and permission evaluation

• API validation and safe concurrency

• CRM and commercial data relationships