What the TrustLayer + Procore integration does
TrustLayer’s Procore integration keeps Procore Companies and Projects in sync with TrustLayer Parties and Projects, and writes TrustLayer compliance status back into Procore.
Procore remains the system of record for Projects, Companies, and Commitments.
TrustLayer remains the system of record for compliance evaluation and compliance status.
Key terms (Procore ↔ TrustLayer)
Company (Procore) = Party (TrustLayer)
Project (Procore) = Project (TrustLayer)
Commitment (Procore) = Party-to-Project association (TrustLayer)
Company Insurance (Procore) = Compliance status (TrustLayer)
Prerequisites
Before you start, make sure you have:
A TrustLayer account.
A TrustLayer user with Organization Admin / Owner permissions.
A Procore user with Company-level permissions to:
Install apps from the Procore App Marketplace.
Manage the Company Directory.
Use the Commitments tool (required for commitment-based linking).
Step 1: Install TrustLayer from the Procore App Marketplace
Log in to Procore.
Open the Procore App Marketplace and search for TrustLayer.
Click Install App.
When prompted, choose which Projects the TrustLayer app can access.
You can skip this during install and add projects later.
Only projects you permit will be visible later in TrustLayer’s Procore integration settings
Step 2: Ensure TrustLayer has access to the right Procore projects (recommended)
After installation, Procore creates a TrustLayer service user (often shown as [email protected]).
In Procore, open Company Tools → Directory.
Search for TrustLayer.
Open the TrustLayer user and click Edit.
In the Project Settings area:
Enable Add TrustLayer to all new projects (recommended).
Add existing projects individually, or use bulk add.
This step ensures new Procore projects will be available to link in TrustLayer.
Step 3: Provide your Procore Company ID to TrustLayer
TrustLayer needs your Procore Company ID to connect the integration.
You can find it in your Procore URL: it is the number after
/app/company/.
Enter your Procore Company ID while in TrustLayer Settings as part of configuring the Integration [email protected].
Step 4: Connect Procore inside TrustLayer
In TrustLayer:
Go to Settings → Integrations.
Select Procore.
Complete the connection.
Choose your configuration options (described below).
Step 5: Map (link) Procore Projects and Companies to TrustLayer
TrustLayer supports two ways to bring Procore data into TrustLayer:
Manual mapping (recommended for initial setup)
In TrustLayer’s integration settings, you can:
Import a Procore Project/Company into TrustLayer.
Link a Procore Project/Company to an existing TrustLayer Project/Party.
Mark items as Do not add to TrustLayer (ignored by the integration).
Automatic import (available for Projects; Companies can also be imported automatically depending on configuration)
If enabled, new Procore projects will automatically become available for linking.
Parties (companies) can also be brought into TrustLayer automatically through commitments (details below).
How data sync works
TrustLayer and Procore sync data in both directions:
Procore → TrustLayer (Projects, Companies, Contacts, Commitments)
Projects: imported from Procore into TrustLayer.
Companies (Parties): imported from Procore into TrustLayer.
Commitments: used to associate a Procore Company to a Procore Project (which then creates the Party-to-Project association in TrustLayer).
Contacts (optional): can sync Procore company contacts into TrustLayer.
TrustLayer → Procore (Compliance status)
TrustLayer writes compliance status into Procore as Company Insurance records.
What exactly syncs from Procore into TrustLayer
Projects (Procore → TrustLayer)
TrustLayer can import and keep these fields updated:
Project name
Project description (configurable behavior)
Start date
Completion date
Project number (as a custom field)
Total value (as a custom field)
Active / inactive status (optional)
Parties (Companies) (Procore → TrustLayer)
TrustLayer can import and keep these fields updated:
Company name
Address
Website
Active / inactive status (optional)
Contacts (optional)
Contacts (optional) (Procore → TrustLayer)
If contact sync is enabled, TrustLayer can import company-level (global) contacts:
First name, last name
Phone
Email
Fax
⚠️ Project-level contacts are not supported. Only company-level contacts sync.
Commitments (Procore → TrustLayer)
Commitments are how Procore indicates that a company is working on a project.
Supported commitment types include Purchase Orders (POs) and Subcontracts / Work Order Contracts (SCs).
TrustLayer uses commitment status rules (configurable) to determine whether a commitment is considered active, and therefore whether to add/associate a Party to a Project in TrustLayer.
How TrustLayer writes compliance status back to Procore
TrustLayer writes compliance status to Procore as one or more insurance records on the Company.
You can choose between two formats:
Option A: Subject format (default)
Procore receives insurance records per compliance subject (example: General Liability, Auto, Workers Comp). This insurance record also includes that status of all requirements associated with that compliance subject.
Each record includes status, dates, policy number, insurer name, and notes when available.
Option B: Summary format
Procore receives one insurance record per compliance subject without the included status of each requirement associated with that compliance subject.
That single record represents overall compliance. For example: CGL = Compliant vs. CGL - Each Occurrence is $1M = Compliant.
What TrustLayer writes to Procore can include:
Insurance type (subject-based or summary)
Effective date
Expiration date
Compliance status
Policy number (subject format)
Insurer name (subject format)
Notes (non-compliant requirements or subjects)
💡 TrustLayer overwrites the Procore insurance record fields it manages. If a user manually edits those insurance records in Procore, the next sync from TrustLayer may replace those manual changes.
Configuration options (what you can customize)
Your TrustLayer Procore integration includes settings for common configuration options.
1) Turn compliance sync on or off
If compliance sync is turned off, no compliance status is written back to Procore.
Projects and Parties can still be linked and imported.
2) Choose the compliance sync level
Choose which level of compliance TrustLayer sends back to Procore:
All: sends global-level and project-level compliance.
Projects only: sends only project-level compliance.
Parties only: sends only global-level compliance.
3) Choose the compliance format (Subjects vs Summary)
Subjects: one record per subject with associated requirements (more detail).
Summary: one overall record (less noise).
4) Contacts synchronization (optional)
You can choose one of the following:
Do not sync contacts (default)
Sync all contacts and set primary
Sync all contacts (do not set primary)
Only sync primary contact
⚠️ Many teams do not maintain a primary contact consistently in Procore. If you select “Only sync primary contact” and no primary contact is set in Procore, TrustLayer may not receive contact data.
5) Ignore commitment types (optional)
If you only want certain types of commitments to create associations, you can choose to ignore:
Purchase Orders (PO)
Subcontracts / Work Order Contracts (SC)
6) Define which commitment states count as “active”
TrustLayer uses “active” commitments to decide when a Party should be associated with a Project.
You can customize:
The shared list of active commitment states.
Separate active state lists for subcontracts vs purchase orders.
Whether “active” is based on status or strictly on executed.
7) Sync active/inactive status from Procore to TrustLayer (optional)
You can choose whether a Procore project or company becoming inactive should also inactivate the linked TrustLayer record.
8) Project description sync behavior
Choose how Project descriptions are handled:
Always keep in sync (default)
Only sync on import (TrustLayer won’t update descriptions after the initial import)
Optional: Compliance profile mapping (Advanced)
If you want Procore data to automatically choose the correct TrustLayer compliance profile when a Party is added to a Project, TrustLayer can support compliance profile mapping.
Typical approach:
Create a custom field in Procore Commitments.
Set the field value to match a TrustLayer compliance profile name exactly.
TrustLayer uses that value to apply the right compliance profile during the Party-to-Project association.
⚠️ This requires exact name matching. Even a small typo can prevent the intended profile from applying.
If you need help setting this up, contact your TrustLayer team or email [email protected].
Troubleshooting
Projects or companies are not showing up in TrustLayer
Check the following:
The TrustLayer app is installed in Procore.
The TrustLayer Procore user has been permitted for the relevant projects.
The Procore project has been added to the TrustLayer app user (or “Add TrustLayer to all new projects” checkbox is enabled).
Companies are not being associated to projects in TrustLayer
Common causes:
The Project is not linked/mapped in TrustLayer.
The commitment is not in an active state based on your integration settings.
The commitment type is ignored by your configuration (PO vs SC).
Contacts did not sync
Common causes:
Contacts sync is disabled.
“Only sync primary contact” is enabled, but Procore has no primary contact set.
The contact is missing an email address.
Compliance status is not appearing in Procore
Common causes:
Compliance sync is turned off.
The company/project is not linked correctly.
You are expecting an update, but the compliance change did not result in a subject-level status change.