Capabilities

• Sync user identities from Verkada to ConductorOne

• Resources supported:

  • Access users
  • Access groups

• Provisioning supported:

  • Access group membership

Add a new Verkada connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, click Connectors > Add connector.

2. Search for Verkada and click Add.

3. 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 ConductorOne)

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

   • Create a new managed app

   Do you SSO into Verkada using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Verkada app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else. Setting multiple owners is allowed.

   A Verkada connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Org Admin permissions in Verkada

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your Verkada connector.

• If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Verkada connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Org Admin permissions in Verkada must perform this task.

Step 1: Generate a Verkada API key

1. In the Verkada , Click Admin Home.

2. Click Verkada API and select + New API Key.

3. Give the new API key a name, such as “ConductorOne integration”.

4. Select the relevant permission:

   • Read/write if you want to use ConductorOne to provision Verkada group membership

   • Read only if you do not want to use ConductorOne to provision Verkada group membership

5. Select an expiration for the API key, then click Generate API key.

6. Carefully and copy and save the new API key. We’ll use it in Step 2.

Step 2: Add your Verkada credentials to ConductorOne

1. In ConductorOne, navigate to the Verkada connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Connectors > Verkada (if there is more than one Verkada listed, click the one with your name listed as owner and the status Not connected).

2. Find the Settings area of the page and click Edit.

3. Paste the API key you generated in Step 1 into the API key field.

4. Select your Verkada region (United States or European Union).

5. Click Save.

6. The connector’s label changes to Syncing, followed by Connected. View the logs to ensure that information is syncing.

That’s it! Your Verkada connector is now pulling access data into ConductorOne.

Configure the Verkada integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Verkada and ConductorOne.

See the ConductorOne Verkada integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.