> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Percipio connector

> C1 provides identity governance for Percipio. Integrate your Percipio instance with C1 for unified visibility and governance over user access.

## Capabilities

| Resource | Sync                                                          | Provision |
| :------- | :------------------------------------------------------------ | :-------- |
| Accounts | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Courses  | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

## Gather Percipio credentials

Configuring the connector requires you to pass in credentials generated in Percipio. Gather these credentials before you move on.

To set up the integration with C1, you'll need:

* Your Percipio organization UUID

* The API bearer token associated with a [Percipio service account](https://documentation.skillsoft.com/en_us/pes/Integration/int_api_rest_authentication.htm)

Please work with your Skillsoft Account Team to set up a service account for the C1 integration and gather these credentials.

**Done.** Next, move on to the connector configuration instructions.

## Configure the Percipio connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Percipio credentials generated by following the instructions above
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Percipio** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Percipio connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        In the **Organization ID** field, enter your Percipio organization UUID.
      </Step>

      <Step>
        In the **API Token** field, enter the token associated with the Percipio service account set up for this integration.
      </Step>

      <Step>
        **Optional.** In the **Course IDs** field, add the ID numbers of the courses you want to sync. If no course numbers are entered, C1 will sync all available courses.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Percipio connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Percipio connector, hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    * [GitHub repository](https://github.com/conductorone/baton-percipio): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Percipio connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Percipio connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Percipio connector deployment:

    #### Secrets configuration

    ```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-percipio-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-percipio-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Percipio credentials
      BATON_API_TOKEN: <Percipio API bearer token>
      BATON_ORGANIZATION_ID: <Percipio organization ID>
      BATON_LIMITED_COURSES: <Optional. Limit synced courses to the course IDs you specify here>
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-percipio.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-percipio
      labels:
        app: baton-percipio
    spec:
      selector:
        matchLabels:
          app: baton-percipio
      template:
        metadata:
          labels:
            app: baton-percipio
            baton: true
            baton-app: percipio
        spec:
          containers:
          - name: baton-percipio
            image: ghcr.io/conductorone/baton-percipio:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-percipio
            envFrom:
            - secretRef:
                name: baton-percipio-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Percipio connector to. Percipio data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your Percipio connector is now pulling access data into C1.
  </Tab>
</Tabs>