Safeguard Docs
Compliance ConnectorsSetup by categoryUser Access Review

ConductorOne

Connect ConductorOne to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Record your ConductorOne connection as user access review evidence. Automated collection is not available for this provider yet.

CategoryUser Access Review
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In ConductorOne:

    1. In the C1 (ConductorOne) web app, open your profile menu and select API keys.
    2. Click Create credential.
    3. Give the API key a name and select whether the key will expire.
    4. Optionally enter allowed IP addresses in the Limit source IPs field.
    5. Under Limit Scopes, select Read-Only Administrator.
    6. Click Create. The client ID and client secret are shown; copy the client secret now, as it won't be shown again.

    Where to find the other values:

    • Base URL (optional): Use your tenant's C1 web app address; C1 states that API hosts and authentication are tenant-specific.

    ConductorOne shows the secret only once, so copy it before you leave the page.

    Source: c1.ai, c1.ai, checked 2026-10-07.

  2. On Compliance › Connectors, open ConductorOne, click Connect, choose API token and fill in:

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. Click Connect with token.

Frameworks

No automated compliance test reads ConductorOne yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

On this page