Skip to main content

How to Configure PIN Settings in the Tenant Admin Portal

This document provides step-by-step instructions to configure the Pin using the Oloid Portal.

Updated over a week ago

Introduction :

The PIN configuration feature in the Oloid Tenant Admin Portal allows administrators to define PIN format, apply complexity rules, control duplicate PIN usage, and configure lockout behavior. This guide provides step-by-step instructions to set up secure and customized PIN policies for user authentication.

Steps to configure the PIN credential:

  1. Log in to the Oloid Portal.

  2. On the homepage of the portal, click user profile icon on the bottom left corner of the menu panel.

    The user profile menu is displayed.

  3. Go to Tenant Settings.

    The Tenant Settings page is displayed.

  4. Go to Advanced tab > PIN.

    Image

  5. On the PIN tab do the following:

    1. Turn on Allow Duplicates option to allow identical PINs for multiple users.

    2. Enable PIN Complexity Rule to restrict using consecutive characters and numbers.

      Note: You can set alphabets, numbers, and special characters as PIN and cannot repeat them more than twice consecutively.

      Example Password: arppp123(wrong); arpp135,b#7f4(correct)
    3. Select Configure Maximum PIN Attempts to set the number of retries allowed for PIN entry.

      Default value : 3

      Max value : 5

    4. Turn on Enable Action on Max PIN Attempts toggle button to block users for the set time duration after maximum PIN attempts are over.

      Default value : 5 min

      Max value : 30 min

    5. Select any one of the Pin Configuration option.

      • Numeric 4 Digit PIN ( Default)

        This allows users to set only 4 digit PIN as credential.

      • Numeric 6 Digit PIN

        This allows users to set only 6 digit PIN as credential.

      • Open PIN

        This allows users to set any character PIN between 8 to 15 characters.

      Note: The default setting is Numeric 4 Digit Pin.

  6. Click Save.

    The PIN configuration is updated successfully.

Did this answer your question?