Specifically, SSO allows users of your organisation to log in to Skore with their usual credentials, typically the Microsoft Azure AD credentials they are using to log into their computer in the morning. The benefit is that they do not need to manage another account / password for Skore.
Additionally, this helps enforce all your security requirements (multi factor authentication, etc.) and easily prevents users who left the organisation continued access to Skore.
Below are the steps required to successfully set-up Single Sign On for your Skore workspace using Microsoft Azure AD.
Skore implementation of SSO relies on recognising email domains. We'll therefore need to understand all the domains potentially used by users of your organisation
Identify the Azure AD administrator
The first user to log into Skore with SSO need to have Azure AD administrative rights in order to approve the Skore application into your IT domain.
Contact us at firstname.lastname@example.org
to provide the list of email domains and the name of your administrator
A Skore agent will setup the system for you and test with your administrator during an online meeting. This takes 15 minutes.
Step 2: Azure AD administrator and Skore agent organise a configuration session.
Ready to go!
Once the administrator has approved Skore and testing is complete, users are ready to go!
Step 3: Users enter their email on the skore login page, and be directed to their usual organisation's login page.
The Azure administrator will be presented with a screen that looks like that. The user will approve for the entire organisatio
(Before this is authorised user will be presented with a message similar o this one
Adding new users
Users can be invited to Skore by a workspace admin, or the workspace can be setup to allow users to join.
If an employee leaves the business, the users account will need to be manually removed from the Skore platform. Nevertheless, providing the account is disabled on your Azure AD already, the user will not be able to access Skore.
Changing user licence / permissions
Changing a users licence / permissions (member, editor) is performed in Skore and is not related to SSO.
- Skore does not support automatic provisioning from Azure AD groups