With SCIM integration people in your organization are automatically added/removed from your SellerCrowd team as you add/remove them in Okta. SCIM enables you to manage your users from a single system (Okta in this case). Changes are propagated to SellerCrowd behind the scenes.
Prerequisites
To have SCIM enabled for your organization an enterprise plan is required (see pricing). You need to be the owner or an admin of your team in SellerCrowd. Once in place, you can access your team account via Billing Team tab (available in Settings, alternatively using this link: https://sellercrowd.com/settings/billing-team/) where you can get following details:
SCIM Endpoint
Access Token (Bearer)
You have to have SellerCrowd application installed in Okta (you can find it in Okta's app directory). See https://help.sellercrowd.com/en/articles/7878055-configuring-sso-using-okta for details on how to find and istall SellerCrowd integration in Okta.
Supported features
Push new users, users you create in Okta are added to SellerCrowd.
Push profile updates, profile updates done in Okta are pushed to SellerCrowd.
Push user deactivation, deactivating or removing a user in Okta removes user from team in SellerCrowd.
Import users from SellerCrowd, users and profiles can be pulled from current billing team.
Configuration steps
In Sellercrowd app in OKTA, go to Provisioning / Integration and click "Edit":
Scroll down to HTTP Header / Authorisation, enter the Bearer Token from Access Token (Bearer) value, available at Sellercrowd's Billing Team page (see Prerequisites),
Click "Save".
Your SCIM configuration for SellerCrowd is complete. From that point on, changes you make to your users in Okta will propagate to SellerCrowd - they will be added / removed from your billing team accordingly.
Note: as a first step, you may consider triggering synchronization of all users in bulk, so that they appear in your SellerCrowd billing team.