Set up a Procore connector

ConductorOne provides identity governance for Procore. Integrate your Procore instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts	✅	✅
Projects	✅	✅
Companies	✅

The Procore connector supports automatic account provisioning.

Gather Procore credentials

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

A user with the permission to create apps in Procore must perform this task.

Create a Procore app

In the Procore Developer Portal, navigate to My Apps > Create a New App.
Give the new app a name, such as “ConductorOne”.
Click Create.
Next, go to the new app’s configuration page.
Click Data Connector Components and click to enable Service Account.
Carefully copy and save the app’s Client ID and Client Secret.

Enable project directories

For each Procore project you want to provision using ConductorOne:

Navigate to the project’s admin settings and click Tools.
Enable the project directory.

That’s it! Next, move on to the connector configuration instructions.

Configure the Procore connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Procore credentials generated by following the instructions above

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Procore and click Add.
Choose how to set up the new Procore 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
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Enter the Procore credentials into the relevant fields.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

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

Follow these instructions to use the Procore connector, hosted and run in your own environment.

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

Step 1: Set up a new Procore connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Procore 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
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Procore connector deployment:

Secrets configuration

# baton-procore-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-procore-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>

  # Procore specific credentials
  BATON_CLIENT_ID: <Procore app client ID>
  BATON_CLIENT-SECRET: <Procore app client secret>

  # Optional: Include if you want ConductorOne 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

# baton-procore.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-procore
  labels:
    app: baton-procore
spec:
  selector:
    matchLabels:
      app: baton-procore
  template:
    metadata:
      labels:
        app: baton-procore
        baton: true
        baton-app: procore
    spec:
      containers:
      - name: baton-procore
        image: ghcr.io/conductorone/baton-procore:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-procore-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Procore connector to. Procore data should be found on the Entitlements and Accounts tabs.

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