Kord is version control for engineering document sets. Point it at a Procore Documents folder and it imports what is there, then watches for changes: every later revision is something you can compare, review, and approve. Kord reads from Procore - it never moves, renames, or deletes anything there.

What the integration does

• See what changed. Side-by-side and overlay diffs for PDF drawings and P&IDs, DWG, Word, Excel, PowerPoint, images, STEP models, and Rockwell PLC projects. Not a file-modified timestamp: the changed line, the moved dimension, the edited cell.
• Review before it ships. Changed files are grouped into a review session - the engineering equivalent of a pull request. Reviewers comment on the drawing, give a verdict, and publishing holds until the required sign-offs land.
• A record you can hand to an auditor. Revision history, comments, and sign-offs for everything that came out of Procore live in one place in Kord, exportable as an audit packet.

Connecting Procore

1. An administrator registers a Procore app and adds its client credentials once, on the organization's Integrations settings. It is configured for the whole organization, not per person.
2. Each member clicks Sign in with Procore and authenticates on Procore's own site. Kord never sees the credentials.
3. Pick the project and the Documents folders to track. Kord imports them in the background and from then on the folder is linked - files keep a live connection back to where they came from, and "Open in Procore" goes straight to the file.

Every member authenticates as themselves, so Kord can only ever read what that person can already read in Procore. Permissions are yours, enforced by Procore.

How sync behaves

Sync runs when someone asks for it. Kord does not poll your Procore project in the background. A new file in the tracked folder shows up marked as new; a modified file is flagged "Modified in cloud" and staged as a new revision to review against the last one you approved. Nothing is ever written back to Procore - reviewing and publishing happen entirely inside Kord, so what you approve there doesn't change what your field teams see in Procore.

Security

• OAuth 2.0 against your own Procore company, scoped to the projects and folders a member has access to. No Procore password is ever seen by Kord.
• Tokens encrypted at rest with AES-256-GCM, rotated on every refresh, and revocable at any time by disconnecting the integration.
• Your app, your company. The client credentials belong to your Procore company. Kord holds no cross-company credential and no back door into your data.
• Scoped to Documents and Projects. Kord doesn't read RFIs, financials, directory, HR, or cost data from Procore - it isn't asked for and it isn't stored.

Requirements

A Procore company with API access, and a Kord account on an Enterprise plan. Setup takes about five minutes and doesn't need anything installed on anyone's machine.

Questions, or want a hand connecting your first folder? Email support@withkord.com or book a demo below - we'll walk through it on a real project of yours.