> ## 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 Verkada connector

> C1 provides identity governance and just-in-time provisioning for Verkada. Integrate your Verkada instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

## Capabilities

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

## Gather Verkada credentials

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

<Warning>
  A user with **Org Admin** permissions in Verkada must perform this task.
</Warning>

### Generate a Verkada API key

<Steps>
  <Step>
    In Verkada click **Admin Home**.
  </Step>

  <Step>
    Click **Verkada API** and select **+ New API Key**.
  </Step>

  <Step>
    Give the new API key a name, such as "C1 integration".
  </Step>

  <Step>
    Select the relevant permission:

    * **Read/write** if you want to use C1 to provision Verkada group membership

    * **Read only** if you **do not** want to use C1 to provision Verkada group membership
  </Step>

  <Step>
    Select an expiration for the API key, then click **Generate API key**.
  </Step>

  <Step>
    Carefully and copy and save the new API key.
  </Step>
</Steps>

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

## Configure the Verkada connector

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

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Verkada 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 **Verkada** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Verkada 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>
        Paste the API key into the **API key** field.
      </Step>

      <Step>
        Select your Verkada region (United States or European Union).
      </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 Verkada connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Verkada 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-verkada): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Verkada 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 Verkada 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 Verkada connector deployment:

    #### Secrets configuration

    ```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-verkada-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-verkada-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Verkada credentials
      BATON_API_KEY: <Verkada API key>
      BATON_REGION: <US (default) or EU>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: true
    ```

    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-verkada.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-verkada
      labels:
        app: baton-verkada
    spec:
      selector:
        matchLabels:
          app: baton-verkada
      template:
        metadata:
          labels:
            app: baton-verkada
            baton: true
            baton-app: verkada
        spec:
          containers:
          - name: baton-verkada
            image: ghcr.io/conductorone/baton-verkada:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-verkada
            envFrom:
            - secretRef:
                name: baton-verkada-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 Verkada connector to. Verkada data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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