Set up authenticator protection

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

Overview

Security Settings manages personal authenticator enrollment and recovery codes. Administrators can configure an organization MFA policy and assist another user with recovery under the required verification controls.

Purpose

Add a second sign-in factor and retain a controlled recovery path.

Prerequisites

• Your current CRM password.

• An authenticator application and a protected place for one-use recovery codes.

• Administrator identity for organization policy or administrator-assisted recovery.

Procedure

1. Open Security Settings and choose Set up authenticator app.

2. Reauthenticate as prompted. Scan the displayed QR code in your authenticator and submit a current code to confirm enrollment.

3. Save the displayed recovery codes in your approved protected location. They are shown only through the designated recovery-code flow.

4. Sign out and sign in again to verify the challenge works.

5. Administrators should check that the affected active users are enrolled before changing the organization policy to require MFA.

6. For a lost factor, use an unused recovery code or contact another administrator. Administrator-assisted reset revokes sessions and requires reenrollment.

Expected result

The account has verified authenticator protection and a known recovery route.

Screenshots and diagrams

SS-049 · Security settings (MFA). Demonstration capture, 28 October 2026. Select the image to enlarge.

Important notes

• Never place QR codes, setup secrets or recovery codes in a support ticket or screenshot.

• Authenticator codes change on a short time interval. Already-used codes are rejected and adjacent clock steps are bounded.

• Personal MFA enrollment and an organization requirement are separate states.

• The screenshot shows a not-enabled example; it does not establish your current policy.

Troubleshooting

• Code rejected: use a fresh code and check the device clock.

• Policy change blocked: complete the enrollment prerequisites for affected users.

• Recovery required: do not share a code with support; follow the authenticated recovery flow.

Related articles

• Sign in and manage your session

• Create and maintain Users

• Use the Settings hub and preferences

• Read System Health and verify service readiness