Kord is version control for engineering document sets. Point it at an ACC folder and it imports what is there, then watches for changes: every later edit becomes a revision you can compare, review, and approve. ACC stays the system of record - Kord adds new and changed files there, but it never renames, moves, or deletes one.

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.
• Issued revisions go back to ACC. Each published revision is uploaded into a Published folder beside the source, so the record of what was issued lives with the files - not in a tool your field team has to log into.
• Additive, on purpose. Kord can create folders and upload new or updated files to ACC. It has no delete, rename, or move path against ACC at all - so it can never be the thing that breaks your common data environment's record of a file.

Connecting ACC

1. An administrator registers an app with Autodesk Platform Services and adds its client credentials once, on the organization's Integrations settings. It is configured for the whole organization, not per person.
2. Each hub admin whitelists that app under ACC Account Admin → Settings → Custom Integrations - a one-time step Autodesk requires before any external app can reach the hub. (Trial ACC accounts don't have this tab, so the integration needs a full ACC subscription.)
3. Each member clicks Sign in with Autodesk and authenticates on Autodesk's own site. Kord never sees the credentials.
4. Pick the project and 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.

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

How sync behaves

Sync runs when someone asks for it. Kord does not poll your hub in the background, and it never touches a file it didn't create without someone asking it to.

• New files and edits apply silently. A file added in ACC shows up in Kord marked as new; a modified file is flagged "Modified in cloud" and staged as a new revision to review against the last published one.
• Publishing uploads, it doesn't move. Because Kord can't rename or move files in ACC, a published revision is uploaded as a new version alongside the current file rather than replacing it in place.
• Deletions are marked, never mirrored. A file deleted in ACC is badged in Kord and stays visible. Kord never deletes anything in ACC itself, in either direction.

Security

• OAuth 2.0 against your own Autodesk account, scoped by Autodesk Platform Services to the hubs and projects a member has access to. No Autodesk 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 hub. The client credentials belong to your Autodesk Platform Services app, whitelisted by your own hub admin. Kord holds no cross-hub credential and no back door into your data.

Requirements

A full ACC subscription (Custom Integrations isn't available on trial or Essentials hubs), an app registered with Autodesk Platform Services, and a Kord account on an Enterprise plan.

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