cidaas Registration Flows

On cidaas, the following registration workflows can be implemented based on the business requirements and user verification needs.

1. Administrator Confirms the user and the user verifies the Email or SMS

2. Auto-confirm the user and the user verifies the Email or SMS

3. Administrator confirms the user and the Email or SMS is auto-verified

4. Auto-confirm the user and Auto-verify the Email or SMS

By default the cidaas service offers the first flow - which is "Administrator confirm user and user verify Email/SMS".

Supported Flows/Logic for New User Registration

To be a valid user in the cidaas system, two verification steps need to be fulfilled:

  1. Administrator Needs to verify the user registration.
  2. Users have to confirm/verify their Email/SMS.

This default behavior can be overridden using some of the customized cidaas flows.

Administrator Confirms the User and User Verifies the Email or SMS

In this flow, once the user registration is completed user MUST confirm the Email/SMS, and wait for admin verification. Once admin verifies the user registration, then user can login into the business-portal/services.

Use Case

The business might need to ensure that the user has a valid email id/mobile number (to send their business related information) or some other confirmation may be needed, where the business needs to check the user back ground info, such as (no dues/payment, physical verification, etc..).

Auto Confirm the user and the user verifies the Email or SMS

In this flow, once the user registration is completed user MUST confirm the Email/SMS and does not need to wait for admin verification. User can immediately login into the business-portal/services.

Use Case

The business might need the user only with the valid email id/mobile number (to send their business related information).

Administrator Confirms the User and Email or SMS is auto-verified

In this flow, Once the user has registered, user email/sms is considered as valid, and user needs to wait for admin verification. Once admin verifies the user registration, user can login into the business-portal/services.

Use Case

The business is not too concerned about the user’s email id/mobile number but at the same time, requires admin verification.

Auto-confirm the User and Auto-verify the Email or SMS

In this flow, once the user has registered they will immediately became a valid user. So that they can login immediately.

Use Case

This flow works well, for businesses where the verification is not required and it is important that the customer is able to login immediately.

Reference Link Refer the create user section, where these flows could be activated.



results matching ""

    No results matching ""