Capabilities
- Users: Synced from
/v2/mgmt/user/search. The stable ID is the DescopeuserId. - Tenants: Synced from
/v1/mgmt/tenant/search. Each tenant has amemberentitlement that C1 can grant to and revoke from users. - Roles: Synced from
/v1/mgmt/role/all, including both project-level and tenant-scoped roles. Each role has anassignedentitlement that C1 can grant to and revoke from users. - Permissions: Synced from
/v1/mgmt/permission/all. Each permission has agrantedentitlement that shows which roles confer the permission. This is read-only. Manage permission-to-role assignments by editing roles in Descope.
Gather Descope credentials
1
Log in to the Descope console as a project admin.
2
Find your Project ID under Project > Settings > Project ID. It starts with
P.3
Create a Management Key under Company > Management Keys, scoped to the project you want to connect. Copy the key. Descope shows it only once.
4
Decide on the Base URL. Use
https://api.descope.com unless you are on a non-default Descope deployment.5
Optional: To limit the sync to specific tenants, find the tenant IDs in the Descope console under Tenants. They start with
T.ProjectID:ManagementKey.
That’s it! Next, configure the connector in C1.
Configure the Descope connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Descope connector is now pulling access data into C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for Descope and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter the required configuration:
- Project ID: Your Descope Project ID. It starts with
P. - Management Key: The management key you created. C1 stores it as a secret.
- Base URL: The Descope API base URL, for example
https://api.descope.com. Do not include a trailing slash or path. - Tenant IDs: Optional. Leave empty to sync every tenant in the project. See Tenant IDs filter.
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Tenant IDs filter
By default the connector syncs every tenant in the project. When you set Tenant IDs, only these tenants are synced: their tenant resources, their memberships, the assignments of roles scoped to them, and the tenant-scoped roles themselves. Project-level roles and every user still sync, because the role catalogue is read in one project-wide call and the user directory is not filtered. The connector checks on every sync that each ID in this field is a tenant in the project. A configured ID that the search does not return fails that whole sync, including users, roles, and permissions, not just that tenant. The error names the ID, so a tenant that was deleted in Descope stops syncing until you remove its ID from this field. An ID that does not exist, or that carries whitespace from a comma-separated value, would otherwise drop that tenant’s resources and membership grants from every sync without an error, because the listing simply returns fewer tenants. Find the IDs in the Descope console under Tenants (they start withT).
Sync behavior
- Paginates
/v2/mgmt/user/searchvia the request-bodyoffset/limitfields (page size 100), terminating on the responsetotal. - Lists tenants, roles, and permissions in single unpaginated calls.
- Lists tenants through
POST /v1/mgmt/tenant/search. With Tenant IDs unset the request carries an empty payload, which Descope documents as returning every tenant. With the field set the request filters bytenantIds, so the response — and the memory it occupies — is bounded by the configured tenants instead of by the project’s tenant count. Without that bound, a project that auto-provisions a tenant per end-user can return a tenant listing large enough to exhaust the connector’s memory. - Fails validation when a configured Tenant IDs value is not returned by
that search. Descope answers an unmatched
tenantIdsfilter with a normal empty result, so without the check a wrong ID would just sync less. - Scopes tenant-scoped roles, resources and walks together. A role scoped to a
tenant that Tenant IDs excludes is not emitted as a role resource (so its
tenant id does not reach C1 in the role display name or the
tenant_idprofile), and its member walk is skipped. Project-level roles (tenant_idempty) are never filtered. The permission → role grants below are derived from the same role catalogue, so they are filtered the same way — a grant never names a role resource that was not emitted. - Reads the role catalogue itself in one project-wide call per sync, cached for the session; the scope filter above is applied to what it emits, not to what it fetches.
- Does not filter the user directory: users are project-level in Descope, and a user can belong to a tenant that is not synced without being scoped to one. Every user is emitted, whoever its tenants are.
- Refuses to grant access outside the sync scope. A project previously synced without Tenant IDs still holds C1 entitlements for every tenant, so a grant request can name an excluded tenant; the connector fails that grant with an actionable error instead of writing it. Revokes are not guarded, so legacy out-of-scope grants can be cleared.
- Resolves tenant and role grants with a server-side filtered
/v2/mgmt/user/searchper resource —tenantIdsfor tenant membership,tenantRoleNamesfor tenant-scoped roles, androleNamesfor project-level roles — so no full user directory is cached in the session store. - Reports tenant membership as direct membership only, via
includeSubTenants: false. A user’suserTenants[]lists only the tenants they belong to directly, so members of a child tenant are not reported against its parent. - Re-checks project-level role holders against the user’s project
roleNames. TheroleNamesfilter matches a role name at any scope, so a user holding the role only inside a tenant would otherwise be reported as holding the project-level role of the same name. - Resolves permission grants from the inline
permissionNameson the role list (cached once per sync; the role list is small and bounded). - Treats HTTP 429 and 5xx as transient and retries with exponential back-off.
- Caps concurrency at
maxParallelFetches: 6.
Provisioning behavior
- Every grant and revoke first resolves the principal’s login via
GET /v1/mgmt/user?userId=…, because the mutation endpoints below take aloginIdwhile user resources are keyed on the stableuserId. - Role assignment (
role→assigned): grants and revokes project-level and tenant-scoped roles via/v1/mgmt/user/update/role/addand/remove(tenant-scoped roles include thetenantId). - Tenant membership (
tenant→member): adds and removes users via/v1/mgmt/user/update/tenant/addand/remove. - Permission → role grants are read-only; manage them by editing roles in Descope.