Enable Single Sign On For Providers
Support avatar
Written by Support
Updated over a week ago

November 13, 2017
Updated:  March 1, 2020

To navigate to the Provider Single Sign On Access, you will need to go to Settings > Single Sign On > Actions > Single Sign On Providers. This navigates to the Single Sign On Management page that will list the available SSO providers. You will need to click on the enable symbol to enable the provider.

Once enabled in your Platform, your provider will be able to manage their internal users via my.sticky.io and be able to manage users via my.sticky.io and not have to create individual users in your Platform via User Account management.

Providers create users in their my.sticky.io portal by navigating to the Menu in the upper right hand corner, clicking on the drop down arrow and select “Groups” as shown in the illustration below:

After selecting your Group Name, they will be brought to the following page which will show a list of all users that have been created. This is where they will create any new users by clicking on “Add User” as shown in the illustration below:

Please note that the users that are created are specific to the Call Center chosen and are NOT the same users as within Settings > User Accounts.

Once the provider creates the user, they will need to provide that user with the login URL and confirmation link for my.sticky.io.

Once the user logs into their my.sticky.io via the provider’s login page, there will be a list of all Platform’s that they have access to. The user just needs to locate the Platform they want to log into, and select “Sign In”. This will automatically log them into that Platform domain with the given department permissions provided.

There are 3 different department templates available to choose from for each user and each have specific permissions, Tier 1, Tier 2 & Supervisor Agent. These permissions will stick to their my.sticky.io user account and be the same for each sticky.io domain they access. The Supervisor Agent will define the permissions for each template/user after creating them.

Did this answer your question?