Skip to main content
C1 provides identity governance for Runlayer. Integrate your Runlayer instance with C1 for unified visibility and governance over who can administer your MCP platform.

​
Capabilities

ResourceSyncProvision
Users
Roles
This connector is read-only: it syncs Runlayer users, the platform’s fine-grained access (FGA) roles, and each user’s role assignments. It does not provision changes back to Runlayer.

​
Gather Runlayer credentials

Runlayer is tenant-scoped. You connect to your own hosted or self-hosted Runlayer instance, not a shared public endpoint.
1
Sign in to your Runlayer instance as a user whose role can read user and role information, such as Super Admin, Security Admin, or Helpdesk.
2
Open Settings > Personal API keys and create a new key. Copy the key value — it is sent in the x-runlayer-api-key header and is shown only once.
3
Note your instance’s API base URL. It is your Runlayer origin with the /api/v1 path, for example https://your-tenant.runlayer.com/api/v1.

​
Configure the Runlayer connector

Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for Runlayer and click Add.
3
Choose how to set up the new Runlayer 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 Runlayer credentials:
  • Base URL: your instance Management API URL, for example https://your-tenant.runlayer.com/api/v1.
  • API key: the personal API key from your Runlayer instance.
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.
Done. Your Runlayer connector is now pulling access data into C1.