Procore

Procore is an industry-leading construction project management platform that centralizes mission‑critical workflows such as RFIs, Submittals, Daily Logs, Drawings, and Specifications across complex projects. The Glean Procore connector brings this data into Glean for permission‑aware search and AI assistance, so project teams, field staff, and back‑office users can quickly find the latest project status, RFIs, submittals, and logs without leaving Glean.

​

Supported objects

The Procore connector indexes core construction data from the following Procore tools (objects).

​

Projects

• Title and project description
• Address and location (country, state)
• Project number and type
• Stage, work scope, sector, and delivery method
• Project value and roles
• Created by / created at / updated at metadata

​

RFIs (Requests for Information)

• RFI number, subject, and project stage
• Questions and answers
• Status and due date
• RFI manager and “ball in court”
• Responsible contractor and distribution list
• Location, specification reference, cost code
• Schedule impact, cost impact and cost impact value
• Created by / created at / updated at / closed date
• Assignees
• Attachments

​

Submittals

• Submittal number, title, and description
• Submittal type and submittal manager
• Responsible contractor and “ball in court”
• Specification section (label and description)
• Final due date, due date, submit‑by date, issue date, received date
• Required on site date, lead time, and any scheduled task references
• Cost code and location
• Approvers (response, type, user, comments, attachments)
• Status and updated at metadata
• Created by / created at
• Attachments

​

Specifications

• Division
• Set
• Number and description
• Issued date and received date
• Revision and updated at metadata
• Revision PDFs (with text extraction for search)

​

Drawings (metadata)

• Drawing set
• Drawing number and title
• Discipline
• Status and obsolete flag
• Drawing date and received date
• Revision number

The connector indexes drawing metadata; drawing binaries themselves are not rendered in Glean. When Procore exposes drawing revision PDFs for Specifications, Glean extracts text content for search.

​

Daily Logs

The connector indexes multiple Daily Log “sub‑tools,” including:

• Weather: date, weather conditions (sky, precipitation, temperature, wind, ground), calamity notes, comments, vendor, status, attachments, created by / at
• Manpower: company, location, number of workers, total man hours, notes, status, attachments, created by / at
• Notes: comments, status, attachments, created by / at
• Delivery: delivery from, contents, delivery time, tracking number, status, updated at, attachments, created by / at

​

Attachments

The Procore connector indexes attachments for key objects where supported by the Procore APIs:

• RFIs – attached documents and images
• Submittals – attachments, including documents routed for approval
• Daily Logs (Weather, Manpower, Notes, Delivery) – attachments
• Specification revisions – PDFs, with text content extracted for search

​

Limitations

• Only Procore content accessible via the configured Procore application and service account is indexed. If the service account cannot see a project or tool, that data will not appear in Glean.
• Permissions are modeled primarily via Procore’s project‑centric permission templates and tool‑level permissions. Highly custom, non‑template permissions require an explicit admin choice during setup (see Permissions & security).
• Procore tools and objects for example, certain change order or punchlist workflows are currently not supported.

​

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 data sources.

Glean connects to Procore via Procore’s REST APIs over HTTPS and 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)

These values are entered into 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 via App Management).
• Be a Glean admin with permission to add and configure data sources.

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)

​

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 provide a name such as “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. Record this Company ID; you will provide it to Glean during setup.

For more information, check this article.

​

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.

​

Configuration and setup in Glean

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

​

1. Start connector setup

1. In the Glean Admin console, go to Data sources > Add data source.
2. Search for Procore and select the Procore connector.
3. Provide a Name and optional Icon for the Procore data source. 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 app.procore.com/).

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.

​

Permissions & security

​

How permissions are enforced

The Procore connector mirrors Procore’s own project‑centric permissions model as closely as possible:

• Project‑level permissions – users see only the projects they can access in Procore.
• Tool‑level permissions – visibility for RFIs, Submittals, Daily Logs, Specifications, and Drawings follows Procore tool permissions and permission templates.
• Template‑based permissions – Procore permission templates assigned to users govern which tools and records Glean will surface for them. These are adhered to by default.
• Custom / non‑template permissions – ad‑hoc, non‑template permission assignments can be honored by enabling the Read access for custom permissions toggle during setup, as described above.

Glean evaluates permissions at query time so that users only see items they are allowed to access in Procore.

​

Data access model

• The connector uses Procore’s APIs with read‑only access, through the Developer Managed Service Account configured in your Procore Developer App.
• Indexed content is stored within your organization’s Glean deployment; no connector data leaves your environment, and Glean enforces least‑privilege read access.

​

Crawling and freshness

The Procore connector uses a combination of periodic crawls and event‑driven updates (where supported by Procore’s APIs) to keep your index fresh.

​

Full crawls

• A full crawl is run approximately once every 7 days by default.
• Full crawls re‑enumerate projects and all supported objects (RFIs, Submittals, Daily Logs, Specifications, Drawings) that are accessible to the service account.

​

Incremental crawls

• Incremental crawls run approximately every 6 hours.
• They fetch newly created or recently updated projects, RFIs, Submittals, Daily Logs, Specifications, and Drawings since the last incremental crawl.

​

Use cases and example queries

Once enabled and crawls have completed, users can ask Glean natural‑language questions or perform keyword searches across Procore content. Example use cases include:

• Project staffing and membership
  • “Who are the project members of Hospital Tower?”
• Open RFIs and routing
  • “What are the due dates for open RFIs on the Hospital Tower project?”
  • “Who is the responsible contractor for RFI 245?”
• Submittal tracking
  • “Show me open submittals for the Hospital Tower project.”
• Specifications and materials
  • “Construction‑related specifications for Hospital Tower.”
  • “What are the composition and materials for the concrete mix design specifications in Hospital Tower?”
• General discovery and context
  • “Hospital Tower project”
  • “Structured steel bolted RFI”
  • “Flooring”
• Daily logs
  • “Daily logs Mon Nov 17”

Because Glean combines Procore with other enterprise sources (e.g., GDrive, Slack, Jira), users can also ask cross‑system questions such as, “Show me all RFIs related to Hospital Tower that were mentioned in last week’s Slack discussions,” subject to permissions.

​

Troubleshooting

​

Error validating Procore credentials during setup

If the Glean Admin console reports an error when you click Save:

• Confirm that the Client ID and Client Secret exactly match the values from your Procore Developer App’s OAuth credentials (after resetting the secret).
• Validate that the Company ID is correct (numeric ID after app.procore.com/ in the browser URL).
• Verify that the Developer App has been promoted to Production and installed into the correct Procore company using the Production App Version Key via the App Management tool.
• Confirm that the app’s Data Connector component has both User Level Authentication and Service Account Authentication enabled with Company Directory Admin permission.

If these steps look correct and validation still fails, capture the error message and contact Glean Support.

​

Some users do not see Procore content they expect

• Check whether those users have the appropriate project and tool permissions in Procore (for example, RFI tool access, Submittals, Daily Logs). Glean will not show content a user cannot access in Procore.
• If your organization relies on non‑template, ad‑hoc permissions, verify whether the Read access for custom permissions toggle is configured as desired in the connector setup (see Figure 1).
• Confirm that the initial crawl has completed and that incremental crawls are running successfully in the Glean Admin console.

​

Data appears stale

• Remember that full crawls run roughly weekly and incremental crawls run roughly every 6 hours; some updates may take up to several hours to appear.
• For urgent issues, you can trigger a manual crawl or contact Glean Support to review connector health.

​

FAQs