{"id":3005,"date":"2025-05-20T18:24:44","date_gmt":"2025-05-20T18:24:44","guid":{"rendered":"https:\/\/wiki.xontel.com\/?post_type=manual_documentation&p=3005"},"modified":"2025-12-12T16:55:03","modified_gmt":"2025-12-12T16:55:03","slug":"users","status":"publish","type":"manual_documentation","link":"https:\/\/wiki.xontel.com\/ar\/documentation\/call-center\/call-center-v-1-x-x\/authentication\/users\/","title":{"rendered":"Users"},"content":{"rendered":"

User List<\/strong><\/p>\n\n\n\n

The User List tab displays all registered users in system and from actions <\/strong>can edit, deactivate or delete users.<\/p>\n\n\n\n

The Deactivate User<\/strong> popup lets you temporarily disable user accounts for a specific time range.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

User activation log<\/strong><\/p>\n\n\n\n

The User Activation Log provides a clear history of when each user account was deactivated and reactivated. This is especially useful for auditing user access and tracking system usage over time.
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Add User<\/strong><\/p>\n\n\n\n

Personal info<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

User Name<\/strong>: A unique login ID for the new user.<\/p>\n\n\n\n

Password<\/strong>: Must meet the following security requirements:<\/p>\n\n\n\n

Confirm Password<\/strong>: Re-enter the password to ensure it matches.<\/p>\n\n\n\n

First Name \/ Last Name<\/strong> (optional)<\/em><\/p>\n\n\n\n

Email<\/strong>: Used for notifications or password recovery.<\/p>\n\n\n\n

Mobile<\/strong>: Useful for SMS notifications or contact.<\/p>\n\n\n\n

\u0627\u0644\u0634\u0631\u0643\u0629<\/strong>: To associate the user with an organization.<\/p>\n\n\n\n

Timezone<\/strong>: Select the user\u2019s appropriate timezone to ensure accurate time-based actions and logs.<\/p>\n\n\n\n

Avatar<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Avatar<\/strong> tab allows you to personalize a user\u2019s profile with an image or icon.<\/p>\n\n\n\n

Click the “Choose File”<\/strong> button to select an image from your computer.<\/p>\n\n\n\n

Permissions<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Receive Email<\/strong>: Enable to allow the user to receive system emails.<\/p>\n\n\n\n

Receive SMS<\/strong>: Enable to receive SMS alerts (e.g., for ticket updates or reminders).<\/p>\n\n\n\n

Use OTP<\/strong>: Enforces One-Time Password (OTP) authentication for secure login.<\/p>\n\n\n\n

Active<\/strong>: Determines if the account is currently enabled. If off, the user cannot log in.<\/p>\n\n\n\n

Superuser Status<\/strong>: Grants full administrative access to the system.<\/p>\n\n\n\n

Is Supervisor<\/strong>: Marks the user as a supervisor.<\/p>\n\n\n\n

Groups<\/strong>: Assign the user to predefined Groups for role-based access.<\/p>\n\n\n\n

User Permissions<\/strong>: Select specific permissions.
<\/p>\n\n\n\n

Agent<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Is Agent<\/strong>: Toggle to identify the user as an agent. Enables additional telephony fields and queue assignment options.<\/p>\n\n\n\n

Force Change Password<\/strong>: When enabled, the user must change their password upon next login.<\/p>\n\n\n\n

Tickets Permissions<\/strong>: Dropdown to assign ticket-level permissions if ticketing system is enabled.<\/p>\n\n\n\n

Queues<\/strong>: Assign the agent to one or more queues for handling incoming calls.<\/p>\n\n\n\n

Extension<\/strong>: Manually enter the PBX extension number that corresponds to this user.<\/p>\n\n\n\n

Phone Topology<\/strong>: Select External phone or Web phone, depending on the system design.<\/p>\n\n\n\n

Extension User Name<\/strong>: Enter WebRTC username registered on the PBX.<\/p>\n\n\n\n

Extension Password<\/strong>: Enter the password for registering this user\u2019s phone.<\/p>\n\n\n\n

End user<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n


<\/strong>The End User tab<\/strong> is used for linking system accounts to external or non-staff users, such as clients, customers, or partner contacts. This is useful in environments where external parties need limited access.<\/p>\n\n\n\n

Is End User<\/strong>: Enable this toggle to mark the user as an end user (not internal staff or agent). End users often have restricted access to Ticket System.<\/p>\n\n\n\n

Is Company Supervisor<\/strong>: When enabled, this user becomes a designated supervisor for their company \u2014 useful for client-side visibility or approval roles.<\/p>\n\n\n\n

Related Contact<\/strong>: Select an existing contact from the dropdown to link this user with their contact.<\/p>\n\n\n\n

Authentication<\/strong><\/p>\n\n\n\n

After creating users, you can typically edit their account settings to enable 2FA (Two-Factor Authentication) \/ CAPTCHA enforcement.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Authentication<\/strong> section provides administrators with tools to strengthen user account security by enabling features like Two-Factor Authentication (2FA)<\/strong> and CAPTCHA<\/strong>.<\/p>\n\n\n\n

Two-Factor Authentication (2FA)<\/h5>\n\n\n\n

When an admin enables 2FA<\/strong> for a user, the system generates a unique QR code<\/strong> linked to the user’s account. This QR code must be scanned using an authentication app such as Google Authenticator, Microsoft Authenticator, or any TOTP-compatible app.<\/p>\n\n\n\n

\n

\ud83d\udce7 The QR code can be automatically sent to the user via email<\/strong>, ensuring a smooth and secure setup process.<\/p>\n<\/blockquote>\n\n\n\n

Once scanned, the authentication app will generate 6-digit codes that the user must enter during login after entering their username and password. This ensures that even if login credentials are compromised, unauthorized access is prevented.<\/p>\n\n\n\n

CAPTCHA<\/h5>\n\n\n\n

The CAPTCHA<\/strong> option helps block automated login attempts. When enabled for a user, they will be prompted to complete a CAPTCHA challenge during login, verifying that the request is from a human and not a bot.<\/p>\n\n\n\n

Together, these features significantly enhance account security and protect sensitive call center operations from threats.<\/p>\n\n\n\n

<\/p>","protected":false},"author":1,"featured_media":0,"parent":3002,"menu_order":0,"template":"","manualdocumentationcategory":[16],"manual_doc_tag":[],"class_list":["post-3005","manual_documentation","type-manual_documentation","status-publish","hentry","manualdocumentationcategory-doc-demo-articles"],"_links":{"self":[{"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/3005","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/manual_documentation"}],"about":[{"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/types\/manual_documentation"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":10,"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/3005\/revisions"}],"predecessor-version":[{"id":8641,"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/3005\/revisions\/8641"}],"up":[{"embeddable":true,"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/3002"}],"wp:attachment":[{"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/media?parent=3005"}],"wp:term":[{"taxonomy":"manualdocumentationcategory","embeddable":true,"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/manualdocumentationcategory?post=3005"},{"taxonomy":"manual_doc_tag","embeddable":true,"href":"https:\/\/wiki.xontel.com\/ar\/wp-json\/wp\/v2\/manual_doc_tag?post=3005"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}