Administration and configuration

Use these articles for Zbix CRM 1.2.0. Review each procedure’s prerequisites and qualification before acting.

• Create and maintain Users — Give each person an individual account with the intended level of access.
• Manage Teams and legacy role policies — Organize account coverage and manager visibility without granting unintended administrative actions.
• Design customer document templates — Create consistent customer-facing documents while preserving already finalized artifacts.
• Import CSV and Excel records — Load a reviewed dataset while identifying validation and duplicate problems before committing records.
• Set up authenticator protection — Add a second sign-in factor and retain a controlled recovery path.
• Use the Settings hub and preferences — Find the correct configuration page without treating every setting as available to every role.
• Configure Pipelines and stages — Model the organization’s sales process and make forecast probabilities and required information consistent.
• Workflows — Use a conditional rule to make follow-up tasks and in-app notifications consistent, or to enroll an eligible Lead or Deal into a published sales cadence. A saved draft has no operational effect until it is published and activated.
• Approvals — Use approvals when a Deal or a protected Blueprint transition requires a recorded decision. Approval is tied to the submitted state; editing the Deal cannot silently carry an older authorization into a changed transaction.
• Blueprints — Use a Blueprint to enforce a repeatable sales process at the record boundary. The control also applies to supported direct, bulk and import paths, so a board move cannot bypass a governed transition.
• Assignment Rules — Use assignment rules for consistent intake ownership while keeping explicit record owners authoritative.
• Business Calendars — Use a calendar when a response commitment or follow-up delay should count working time rather than elapsed clock time.
• Sales Cadences — Use cadences for a repeatable new-lead or Deal follow-up sequence, with optional completion gates and business-time delays.
• SLA Policies — Use a policy to track first-response timeliness and expose overdue work. Recording an activity is not evidence that a real customer interaction occurred.
• Escalation Rules — Use escalation for due-soon reminders and missed-response follow-up to the record owner or a named authorized colleague.
• Fields and Layouts — Use fields to capture organization-specific information, and layouts to organize forms without changing the database schema manually.
• Module Permissions — Use a custom module role when the standard admin, manager, sales or readonly defaults do not match an operational role. Review access as a whole before assignment.
• Activate and review a self-hosted license — Activate an approved license and verify that the installation has the intended commercial entitlement before customer use.
• Renew licenses transfer installations and manage seats — Keep entitlement current while avoiding seat-allocation failures or an unsupported transfer to a different installation.