Once Okta SSO is set up on your instance, your team can decide to turn on provisioning. Provisioning can be used to manage the users that have access to the Saleshood instance and user information. This article will give you information about provisioning Okta SSO in the production environment of an instance.

Requirements

1. For customer:
   1. An account on Okta
   2. Have SSO setup and working on Okta with SalesHood. To learn how to configure Okta SSO for your instance here.

Notes

1. Users without Titles will have blank Titles in SalesHood
2. Users with no Manager assignment, or their Manager does not yet exist in Saleshood will be assigned a default manager
   1. Default Manager = The first Coach user added to the instance
      1. Can be changed to any user (if manager role or above) by emailing support@saleshood.com
3. If a user has a manager and the manager is provisioned into SalesHood, a team is created with all users of the same manager

Steps

1. In your Okta Saleshood Application, select Provisioning tab and click on Configure API Integration.

2. Check Enable API Integration

3. Enter your instance’s SCIM Token in the API Token field. To learn how to pull a SCIM Token for your Saleshood instance, go here

4. Click on Test API Credentials after inputting API Token

• If you got Saleshood was verified successfully! message then click save
• If you got Incorrect credentials, please verify and try again, please contact Saleshood’s support

5. Click on To App > Edit and enable Create Users, Update User Attributes, Deactivate Users then click save.

These can be turned on/off based on need of customer. For example, do not want to de-activate users? Check this off

6. Lastly, assign people to your app.

Assigning users to the app (SalesHood) will provision them based on the settings above. Users will be de-activated on Saleshood when they are removed from the app.