Kord is version control for engineering document sets. Point it at a SharePoint document library and it imports what is there, then watches for changes: every later edit becomes a revision you can compare, review, and approve. SharePoint stays the system of record - Kord never moves, renames, or deletes a file without someone asking it to.

What the integration does

• See what changed. Side-by-side and overlay diffs for the formats an engineering package is actually made of - PDF drawings and P&IDs, DWG, Word, Excel, PowerPoint, images, STEP models, and Rockwell PLC projects.
• Review before it ships. Changed files are grouped into a review session - the engineering equivalent of a pull request. Reviewers comment, give a verdict, and publishing holds until the required sign-offs land.
• Comments end up in the file. Comments on a Word or Excel document sync both ways with the file's own native comments, so someone working in Office against SharePoint sees the review without opening anything else.

Connecting SharePoint

1. Each member clicks Sign in with Microsoft - the same connection OneDrive uses. If they've already connected OneDrive, SharePoint is already authorized; there's nothing extra to grant.
2. Pick a site and the document library to track. Kord imports it in the background and from then on the library is linked - files keep a live connection back to where they came from, and "Open in SharePoint" goes straight to the file.
3. A personal Microsoft account (an @outlook.com-style login, not a work or school account) can't browse SharePoint sites at all - that's a Microsoft Graph restriction, not a Kord one. Connect with the work or school account that already has access to the site.

How sync behaves

Sync runs when someone asks for it. Kord does not poll your tenant in the background, and file content never moves on its own.

• New files apply silently. A file added to the linked library shows up in Kord marked as new.
• Edits become a review session. A modified file is flagged "Modified in cloud" and staged as a new revision to review against the last published one.
• Deletions are marked, never mirrored. A file deleted in SharePoint is badged in Kord and stays visible. The deletion only takes effect when a review session containing it is published.

Security

• OAuth 2.0 against your own Microsoft tenant, requesting only the Graph scopes needed to read and write the sites and folders you connect. No Microsoft password is ever seen by Kord.
• Tokens encrypted at rest with AES-256-GCM, scoped to the individual user who granted them, and revocable at any time by disconnecting the account.
• Where the bytes sit. Kord keeps its own version history of the files you track, so it can diff a revision against one deleted upstream months ago. Enterprise plans can keep that history in their own S3 bucket instead.

Requirements

A Microsoft 365 work or school account with access to the site you want to track, and a Kord account. Setup takes under a minute and doesn't need anything installed on anyone's machine.

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