Single Sign-On (or SSO) provides us the ability to have one master bot user, which syncs the data between all of your bot users in different channels. This helps vastly in syncing data and identifying bot users when multiple channels are involved.

Enable SSO Login Inside OCP

You can enable SSO by going inside the “Settings” tab on the bottom-left of your Flow builder side menu. Then clicking on the “SSO Settings” option.

Setting Up SSO Login Flow

Click on the “Basic” tab and fill in the required details.

Once done, Create a new sub-flow. Here we will set up the SSO logic.

Once SSO is enabled, you will start seeing “SSO Required” in the Start nodes of the sub-flows. Enabling this option will direct the user toward the SSO login and then redirects the user to the sub-flow you selected inside the settings upon successful login.

Once successful, the “Thankyou” screen will persist for 5 seconds and then the user will be redirected to the follow-up subflow, or you can manually exit the page as well.

Advanced Settings For SSO

Advanced options enable you to set up your own logic flows for SSO. This enables the user to setup the SSO in channels where buttons with links are not properly populated by using a system variable field called “SSO Url”

Syncing Of Data Between Users

The bot user with the SSO tag is the master user which syncs the data between the same bot user in different channels.

If you add a tag or change the value of a variable for the SSO user, the change is also done for bot users in other channels.

If you add a tag or change the value of a variable for the bot user in other channels, the change is also done for the SSO user.

This allows users to sync data between multiple channels across bot users and gives more flexibility when working over multiple channels.

The bot users are still counted separately. SSO only functions to sync the data between bot users, it does not accumulate the bot users into one bot user.