Frequently asked questions

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience CRM users and sales teams · Deployment All supported models

Overview

These answers address common differences between what users see in a list, what a document status means and which actions require administrative help.

Purpose

Resolve frequent onboarding questions before changing data or requesting broader access.

Prerequisites

• Access to your own workspace.

Procedure

1. If a colleague sees more records, compare effective role and own/team/organization visibility. Ask for the specific access needed for your work.

2. If a saved view or report is shared, remember that it shares a definition and still respects the viewer’s record and field permissions.

3. If a Quote is Sent, verify whether an Email Activity was separately queued. The quote status alone does not send mail.

4. If an email is Accepted, inspect provider history when delivery is important. Accepted is submission acknowledgment, not inbox receipt.

5. If a payment is recorded, reconcile it with the actual transaction. CRM payment history does not charge the customer.

6. If a record or commercial document is locked, use its revision, transition or approval workflow rather than creating an unlinked duplicate.

Expected result

You can distinguish expected product controls from problems that need support.

Important notes

• An empty screenshot or list does not mean a capability is missing.

• A role title is insufficient to infer permissions; inspect effective access.

• The documentation describes the release baseline, while your organization controls published layouts, stages and enabled capabilities.

Troubleshooting

• Still blocked: record the page, operation, time and exact safe error message. Include a redacted screenshot and ask your administrator to verify access and version.

• Do not attach passwords, authentication codes, tokens, private keys or unredacted configuration to a support request.

Related articles

• Navigate lists and records

• Module Permissions

• Create and send Email Activities

• Issue Invoices and record payments

• Collect useful support evidence