The purpose of this article is to provide information to Outreach Admins regarding SCIM provisioning.
- Outreach Admins
Automated User Provisioning FAQs:
Q: Is the SCIM API different from APIv2?
A: Yes, SCIM API is different from APIv2. They are different API frameworks and provide different endpoints.
Q: Can I use both SCIM and the CRM Plugin with Use Sync enabled?
A: Yes. The integrations will connect the two users based on their username. Users created over SCIM can also be mapped to a User in Salesforce or Dynamics. You can leverage the CRM plugin for existing supported scenarios (e.g., User creation, role assignment) and the SCIM integration to support additional scenarios (e.g., profile assignment, locking/unlocking of users).
Q: My identity provider does not support SCIM integration. Does this mean I am not able to use the SCIM API?
A: While using an identity provider that supports SCIM already would reduce setup costs, you can still leverage the new SCIM API but build an integration directly against the API.
Q: What does locking / unlocking a User mean?
A: A locked User in Outreach means the User account is not active for a person/application to log into. This also means a locked User does not count against your available number of seats for your Org. When a User in Outreach is unlocked, the User account becomes active and a person/application is able to log into. This also means an unlocked User counts against your available number of seats for your Org. For more information regarding the seat management, refer to the Outreach Seat Management Process article.
Q: Will SCIM API let me manage Outreach Profile and Role configurations?
A: No. Profile and Roles need to be created and configured as desired in Outreach prior to assigning them to Users. For more information regarding user profiles and roles, refer to the Governance Profile Settings Overview article.
Q: Can I delete Outreach Users via SCIM API?
A: No. User deletion is not supported via the SCIM API. Instead, the Outreach User should be updated to a locked state; thereby deactivating the User and preventing the User Account for logging into Outreach. For more information on deleting users, refer to the Outreach Seat Management Process article.