Procore setup

Set up the Procore connector:

• Confirm the requirements.
• Create and install a Procore Developer App with a Developer Managed Service Account.
• Configure the connector in Glean.

Requirements

Technical requirements

To use the Procore connector, you need:

• A Procore company account where you can create a Developer Managed Service Account and a developer app.
• Admin access in Procore to configure Developer Apps and App Management.
• A Glean deployment with access to the Admin console to manage connectors.

Glean connects to Procore with Procore’s REST APIs over HTTPS. It stores indexed data in your organization’s Glean deployment.

Credential requirements

The connector uses OAuth 2.0 credentials from a Procore Developer App that has an associated Service Account:

• Client ID (from your Procore Developer App OAuth credentials)
• Client Secret (generated by resetting the client secret in your Procore Developer App)
• Procore Company ID (numeric ID from your Procore URL, see below)

Enter these values in the Procore connector setup in the Glean Admin console.

Permission requirements

To configure the connector end‑to‑end, the person performing setup must:

• Be a Procore admin for the relevant company (to create developer apps and install them with App Management).
• Be a Glean admin with permission to add and configure connectors.

Within Procore, the Developer App must be configured with a Data Connector component that has:

• User Level Authentication and Service Account Authentication
• Company Directory Admin permission (required for crawling Custom Field Definitions and project directory‑related data)
• Read access for the app user (Developer Managed Service Account) on every project you want to index, including all supported tools: Projects, RFIs, Submittals, Specifications, Drawings, and Daily Logs. To assign the user to projects:
  • If your Procore environment shows an Add All button, use it to add the user to all relevant projects at once.
  • If Add All is not available, add the user to each project manually.

Procore setup (Developer Managed Service Account)

Before configuring the connector in Glean, you must create and install a Procore Developer App with an associated Developer Managed Service Account.

1. Create a Developer App and Service Account in Procore

1. Sign in to your Procore account as an admin and open Procore Developer Apps.
2. Click Create a New App and name it Procore Glean.
3. In the Configuration Builder, go to Data Connector Components and click Add Component.
4. Under Component Type, select both:
   • User Level Authentication
   • Service Account Authentication
5. Then grant the Company Directory Admin permission and click Save Component. This is required to allow Glean to crawl Custom Field Definitions.
6. Click Create Version and then Create App to create the developer app version.
7. Click Promote Version to promote it to a production app version.

2. Generate OAuth credentials

1. In your Procore Developer App, open OAuth Credentials.
2. Click Reset client secret in the OAuth Credentials section to generate a new client secret.

Ensure that you reset the client secret for OAuth Credentials, not the Sandbox OAuth Credentials.

3. Copy the Client ID and Client Secret.
4. You will paste these values into the Procore connector setup page in the Glean Admin console.

3. Find your Procore Company ID

1. From your browser, navigate to your Procore web application.
2. The Company ID is the numeric value immediately after https://app.procore.com/ in the URL.
3. Save the Company ID to provide to Glean during setup.

For more information, see find the company ID.

4. Install the app into your Procore company

1. Go back to the Configuration Builder for your Developer App and copy the Production App Version Key.
2. In the Procore web UI, switch to the Company that you want to connect to Glean.
3. Open the App Management company tool.
4. Click Install App, paste the Production App Version Key, and click Install to add the Glean app to your Procore environment.

At this point, Procore is prepared for Glean to connect via the Procore APIs using your Developer Managed Service Account.

5. Add the app user to projects

After installing the app, add the Developer Managed Service Account (DMSA) app user to every project you want Glean to index.

1. In the Procore web UI, go to Company level → Directory.

2. Locate the app user for your service account. For example, if you named the service account "Procore Glean," look for a username similar to procore-glean-... in the directory search results; this user’s first and last name fields are often blank.

3. Apply a permission template (or explicit permissions) that grants at least Read access to the following tools:

   • Projects, RFIs, and Submittals
   • Specifications, Drawings, and Daily Logs

4. Select the Add Integration <app-user-name> to all new projects checkbox. This ensures the app user is automatically added to any future projects you create.

5. Assign the user to projects:

   • If an Add All button is available, use it to add the user to all relevant projects at once.
   • If Add All is not available, add the user to each project manually.

Configure Glean

Once Procore is configured, complete setup in the Glean Admin console.

1. Start connector setup

1. In the Glean Admin console, go to Connectors > Add connector.
2. Search for Procore and select the Procore connector.
3. Provide a Name and optional Icon for the Procore connector. This label will appear for users in search results.
4. In the Procore connector setup page, supply the credentials collected earlier:

• Client ID – your Procore Developer App OAuth Client ID.
• Client Secret – your Procore Developer App OAuth Client Secret.
• Company ID – numeric Company ID from your Procore URL (the number after https://app.procore.com/ in the URL).

Glean uses these values to authenticate to the Procore APIs via the Developer Managed Service Account.

2. Configure custom permissions

Click Manage data (optional). Toggle Read access for custom permissions.

This toggle controls how Glean handles Procore users and access patterns that are not based on standard permission templates.

• By default, Glean honors Procore’s project‑level and template‑based permissions; users see only what they can access in Procore.
• For users or edge cases not governed by templates (for example, ad‑hoc access at the tool level), your admin can choose to provide read access via this toggle so that those relationships are respected in search results, rather than being treated as missing permissions.

3. Save and start the initial crawl

1. Review your configuration.
2. Click Save to complete setup.
3. Glean will start an initial full crawl of Procore content. Once this finishes, Procore results will begin to appear in users’ Glean search and AI experiences.