(Roles Required: Owner, Administrator, User Manager, Help Desk, EPCS Enroller)

Users are the one who use the AuthX Authentication services (Two Factor/Password less Authentication) to log onto different applications protected by the company.

User Grid

1. The Users section shows user metrics like- Total Users and Not Enrolled
   1. Total Users are the number of active users in the company.
   2. Not Enrolled are the number of users whose enrollment is still pending.
2. Below the metrics is the user grid. The user grid lists – Username, Name, Email, Locked Status, Status of user, Source type, Last Login and Actions that can be taken
   1. Username: unique for every user in a company.
   2. Name: Name of the user which includes first name and last name
   3. Email: The email address of the user is used to login into applications. The email address is also a form of communication for the user.
   4. Status: A user’s status can be Active, Inactive and Locked Out.
      1. Active- A user’s status is active in the following situations:
         1. When the user has been enrolled.
         2. When the user is actively using the AuthX services. (Which is based off the user’s last login)
      2. Inactive- A user’s status is inactive in the following situations:
         1. When the user hasn’t enrolled.
         2. When the user hasn’t used AuthX services recently (Determined through last login and user settings).
         3. When the user has been deactivated.
      3. Locked out- A user’s status is locked out in the following situations:
         1. When the user fails to authenticate himself a few times and is locked out as a result. (Determined through the user settings)
   5. Source Type: The source of how the user was added.
      1. In-Cloud – When the users are added through the portal (i.e using the Add User button).
      2. AdSync – When the users are added through Azure Directory sync.
      3. Gdsync – When the users are added through Google Directory sync
      4. On-Prem – When the users are added through LDAP application.
   6. Last Login: Last login is the timestamp of the when the user last logged into any application (and not just portal). If the user hasn’t enrolled, then the last login will be Never Authenticated.
   7. Delete – An option to delete the user by Owner / Admin.
3. Search – Use this search filter to pull the exact records you required
4. Advance Search
   1. You can search the values by inputting the following details: User name, First Name, Last Name, Email, Status & Source Type
      1. After providing the inputs, click Apply – Respective values will be listed on the grid
      2. After providing the inputs, click Clear – Given values will be cleared
   2. Reset – Given values on the Search & Advance Search will get reset & the page will be refreshed
5. This page also has the provision to add a user manually by the Add User button in the top right-hand corner.
6. Import Users – Refer Here
7. Export Users – On selection, the list of users available will be exported / downloaded in the CSV file

Add a user (In-cloud)

(Roles Required: Owner, Administrator, User Manager)

The administrator adds a user manually or through the portal using the Add User button

Username

1. The first step in adding a user is to fill in his username.
   1. The username is checked for uniqueness and should be unique for each user in a company.
   2. The username should be minimum of 6 characters and shouldn’t exceed 20 characters.
   3. The username can contain alpha numeric characters.
   4. The username can be an email address.
   5. The admin clicks on the Add User button to proceed to the next step in adding a user.

Profile Set Up

1. First Name
   1. User’s first name. This is a mandatory field.
2. Last Name
   1. User’s last name. This is a mandatory field.
3. Email
   1. User’s email address, which will be used for all the notification purposes.
   2. The user must use his email address to login to the portal.
4. Alias Username
   1. Username alias is not a mandatory field.
   2. A user can have up to 4 username aliases.
   3. User can use his username alias to authenticate into applications.
5. Primary Username
   1. Primary username is the user’s principal name.
   2. This is not a mandatory field.
   3. User can use his primary username to authenticate into applications.
6. Groups
   1. Admin can assign groups to a user, by clicking on the Add Groups section.
   2. Users can belong to multiple groups.
   3. If a user doesn’t belong to any group, default global policy will be applied.
7. Password
   1. Only if this option is enabled in Settings-> Admin → Allow Admin to Assign Password, this Password field will be displayed

      

   2. Admin / Owner can either choose – Auto Generate password or Let me create the password
      1. Auto Generate password – Random 10 digit password is generated for that particular user & the same will be sent in email to the user
      2. Let me create the password – Admin / Owner can set any password for that particular user & the same will be sent in email to the user
8. Send the sign in information to
   1. You can also send this login info details to another email address which are mentioned here
9. Notes
   1. Notes is not a mandatory field.
   2. Admin can write notes about the user in this space.
10. Phone Number
    1. This is a mandatory field.
    2. Admin can add users phone number in this field.

How to Enroll Auth Factors?

Fingerprint Authentication

1. Click Add fingerprint on computer

   

2. Choose any finger and enroll it

   

3. Then click Finish to save the enrolled finger’s

   

Face Authentication

1. You can enroll your face on computer and AuthX mobile app
2. Click Add face on computer

   

3. Look at the camera & keep your face within the grid to enroll successfully

   

4. Click Continue to enroll the face

   

5. Click Add face on mobile

   

6. A notification will be received. Approve it

   

7. Keep the face within the grid to enroll successfully

RFID Authentication

1. Connect your RFID reader
2. Click Add RFID

   

3. Place your card on the reader

   

4. Card enrolled successfully

Pin Authentication

1. Click Add Pin

   

2. Input 6 digit pin to use it

   

3. Options
   1. Change Pin – Update to new pin
   2. Activate & Deactivate – Current pin will be active / inactive

      

Hardware Token Authentication

1. Go to Authentication Devices and add an Hardware token

   

2. Now come back to Users & click Add Hardware Token

   

3. Select your device & provide the OTP value

   

4. Token added successfully

Protected Web Applications

1. Click View Web Application

   

2. Added web applications by the User to be listed here

   

After Adding User

The following are what happens once a user is added in-cloud or manually:

1. User’s information appears in the user grid, where status shows as Inactive and last login shows as Never Authenticated.
2. The user appears in the pending enrollments grid.
3. The Not Enrolled metrics count is increased by one.
4. An enrollment email is sent to the user’s email address provided by the admin.

In-Cloud User Enrollment Workflow

The following are steps for users added manually to enroll in AuthX:

1. Enrollment Email
   1. User receives an enrollment email to his mailbox.
   2. Below is the template for the enrollment email.

      

2. Redirected to AuthX Page
   1. When the user clicks on the enrollment link, the user is directed to the AuthX portal.
3. Create a Password
   1. The user is directed to the Create a Password page.
   2. The user creates a password and confirms it.

      

4. Mobile Number
   1. The user enters his phone number.

      

5. QR Code
   1. The user sees a generated QR Code.
   2. User installs the AuthX mobile app and scans the QR code.

      

6. Scanned QR Code
   1. The user scans the QR code.
   2. If the QR code is scanned successfully, the QR code has a green check mark and an account is created on the mobile app.

      

Edit User

(Role Required: Owner, Administrator, User Manager)

Admins can edit a user’s profile by clicking on the username of the user. Admins can also see Account Creation and Last Login details:

1. Account Creation
   1. Account creation is the timestamp when the user was created or when the admin clicked on the add user button in the username page.
   2. The time zone of the timestamp will be taken from the company’s general settings.
2. Last Login
   1. Last Login is the timestamp of the user’s last login into the portal or any other applications.
   2. The time zone of the timestamp will be taken from the company’s general settings.
   3. When the user is being created, last login will be Never Authenticated.

1. Admin cannot edit, users first name, last name, username aliases and primary username.
2. Admin can however add username aliases, add groups for a user.
3. Admin remove groups assigned to a user here too.
4. Admin can edit user’s email address and notes.
5. If a user changes his number (just his number and not his device), then the admin can edit the number in the phone number field and save changes. The phone number in the phones grid should change too
6. Admin can delete user’s phone for reasons mentioned below- which will lead to the delete phone workflow (Delete Phone Workflow).
7. Reasons for deleting Phone
   1. User changed his phone (Device) -> Delete Phone Workflow.
   2. User changed his phone number -> Delete Phone Workflow.
   3. User lost his phone and wants to disable the phone from being used->Delete Phone Workflow.
   4. User deleted the accounts in the app -> Delete Phone Workflow.
   5. Admin can enroll user’s bio metrics and deactivate them.

Delete Phone Workflow for user

(Role Required: Owner, Administrator, User Manager)

1. Admin can delete user’s phone by clicking on the trash symbol in the edit user page

   

2. A confirmation pop up appears for the admin to confirm once again. If no is chosen the phone is not deleted, when yes is chosen the phone is deleted.
3. Once the phone is deleted- two things happen:
   1. Register user receives a Phone Number Deleted email

      

   2. The status of the phone changes to Inactive from active and in the action column there is an option “Send Enrollment Email & Send Enrollment Message”. After clicking on Send Enrollment email, an email would be triggered for the respective user to activate Phone.
      1. User is sent an Enroll Phone Number email. Below is the template for the Send Enrollment Email. On selecting the activation link, the respective user receives an Activate phone email.

         

      2. Select Activation link from the email, it will redirect to Phone number page (if needed, update the phone number)

         

      3. For activating, either scan QR code or Generate OTP method

         

      4. After scanning the QR code successfully, green tick mark displays on the QR code

         

      5. After click on continue, it redirects to Confirm your identity page. Use anyone of the authentication factors to login.

         

Inactive User (In-Cloud User)

(Role Required: Owner, Administrator, User Manager)

The admin can make the active user to Inactive, by clicking the toggle

1. Users status will be changed to inactive.
2. The user is no longer able to login into the portal.