Capabilities
The connector syncs your RudderStack SCIM users and groups, and each user’s
group memberships. It is read-only and does not provision access.
The connector reads identity data through RudderStack’s SCIM 2.0 API, which
requires the Enterprise plan with SSO enabled. It surfaces SCIM group
membership; the built-in workspace member/admin role is not exposed by the SCIM
API and is therefore out of scope.
Gather RudderStack credentials
1
In RudderStack, go to Settings > Organization > Service Access
Tokens and select the Organization tab.The token must be an organization-level Service Access Token. A
workspace-level token cannot access the SCIM API and will fail. This is also
separate from a Personal Access Token.
2
Create a new organization-level Service Access Token and copy its value. The
connector sends it on every request as
Authorization: Bearer <token>.3
Note your RudderStack SCIM base URL. For RudderStack Cloud (US) this is
https://api.rudderstack.com/scim/v2.Configure the RudderStack connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your RudderStack connector is now pulling access data into C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for RudderStack and click Add.
3
Choose how to set up the new RudderStack connector.
4
Set the owner for this connector.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter the RudderStack credentials:
- RudderStack SCIM base URL: Your RudderStack SCIM 2.0 base URL
including the
/scim/v2suffix, for examplehttps://api.rudderstack.com/scim/v2. - RudderStack SCIM token: The organization-level Service Access Token you created.
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.