Finalizing your Procore integration

Installing Paladin from the Procore Marketplace connects the two systems, but data will not begin syncing until a few setup steps are complete. Most of them take
place in Procore and can be done by your Procore company administrator in about 15 minutes.

Before you start

You will need:

• A Procore user account with company administrator permissions
• Your Procore Company ID (see Step 3)
• The name of your Paladin account manager

Step 1 — Find the Paladin service account in your Company Directory

When the app is installed, Procore adds a Paladin service account to your company.

1. In Procore, go to Company level → Directory → Users.
2. Search for the Paladin service account. It appears as a standard user record.

If you do not see it, the installation has not finished. Wait a few minutes and
refresh, or contact your Paladin account manager.

Step 2 — Grant the service account permission

The service account needs company-level access to the tools Paladin reads from and
writes to. Assign it a company permission template that grants Admin on:

Tool	Why it is needed
Directory	Read vendor and company records attached to your subcontracts
Companies	Match Procore vendors to Paladin company records
Documents	Upload certificates and contract documents to the project Documents tree
Insurance Manager	Create and update insurance records on subcontracts

Paladin does not create, modify, or delete Procore projects, and does not need project-creation permissions.

To assign the template:

1. Open the service account’s record in the Company Directory.
2. Under Permissions, select or create a company permission template
   with the access listed above.
3. Save.

Step 3 — Send Paladin your Company ID

Your Procore Company ID is the numeric value in the URL when you are working at the company level. For example, in:

https://app.procore.com/1234567/company/home

the Company ID is 1234567.

Send this number to your Paladin account manager. Paladin uses it to direct every API request to the correct Procore company.

Step 4 — Confirm which projects should sync

Paladin pulls projects from Procore based on their project stage. Tell your account manager which of the following should be included:

• Pre-Construction
• Course of Construction
• Post-Construction
• Warranty
• Bidding

Projects in stages you do not select are ignored. Most customers exclude Bidding, since those projects have not been awarded.

Step 5 — Provide a notification contact

Give your account manager one or more email addresses that should receive notifications if a sync fails or needs attention. These usually go to whoever manages subcontractor insurance compliance.

Step 6 — Check that your subcontracts have vendors attached

Before your first sync, review your active subcontracts and confirm each one has a vendor assigned in Procore.

What happens next

Once you have completed the steps above, Paladin will:

1. Register your company in the integration and load your credentials
2. Set the starting date for the first sync
3. Match your existing Procore projects and subcontracts to their Paladin records
4. Enable scheduled syncing and confirm the first successful run with you

Your account manager will confirm when syncing is live.

What syncs, and in which direction

From Procore into Paladin

• Projects — in the stages you selected in Step 4
• Subcontracts — along with the vendor on each one. Purchase orders are not synced, and neither are subcontracts in Terminated or Void status.

From Paladin into Procore

• Insurance records — created and kept current on each subcontract in Insurance Manager
• Contract and compliance documents — certificates, W-9s, and related files uploaded to the project Documents tree and attached to the subcontract

Paladin never creates or edits Procore projects or subcontracts. It reads them, and writes back insurance and document records.

Need help?

Contact your Paladin account manager. They will escalate integration issues to the technical team that maintains it.