Kord is version control for engineering document sets. Point it at an Egnyte folder and it imports what is there, then watches for changes: every later edit becomes a revision you can compare, review, and approve. Egnyte 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. 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.
• 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 Egnyte sees the review without opening anything else.
• Issued revisions go back to Egnyte. Each published revision is written into a Published folder beside the source, so the record of what was issued lives with the files - not in a tool your project team has to log into.
• Transmittals carry your metadata. Kord reads the metadata namespaces configured on your Egnyte folders and writes the values back onto the file's Egnyte properties.

Connecting Egnyte

1. An administrator adds your Egnyte domain and an API key (client ID and secret from your Egnyte admin console) once, on the organization's Integrations settings. It is configured for the whole organization, not per person.
2. Each member clicks Sign in with Egnyte and authenticates on Egnyte's own site. If your domain enforces SSO, Egnyte hands off to your identity provider; if it doesn't, members sign in with their Egnyte password. Kord never sees the credentials either way.
3. Pick the folders to track. Kord imports them in the background and from then on the folder is linked - files keep a live link back to where they came from, and "Open in Egnyte" goes straight to the file in the Egnyte web UI.

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

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 and renames apply silently. A file added in Egnyte shows up in Kord marked as new; a rename or a moved folder is followed rather than read as a delete plus a new file, so the version history stays attached to the document.
• 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 Egnyte is badged in Kord and stays visible. The deletion only takes effect when a review session containing it is published, so nothing disappears from the record because someone tidied a folder.

The Published folder

Turn it on per project and every revision published through a review session is copied into a Published folder inside your linked Egnyte folder, named Drawing_Rev 3.pdf. The current file stays where it has always been - people keep working on it in place - and the Published folder accumulates the issued history. The folder name is configurable, and the whole thing is off by default.

Security

• OAuth 2.0 authorization code flow against your own tenant, with the Egnyte.filesystem scope and a single-use state nonce. No Egnyte passwords are stored.
• Tokens encrypted at rest with AES-256-GCM, scoped to the individual user who granted them, and revocable at any time by signing out or removing the integration.
• Your keys, your tenant. The API key belongs to your Egnyte domain. Kord holds no cross-tenant credential and no back door into your data.
• A well-behaved API client. Calls are rate limited to Egnyte's published limits, respect Retry-After on throttling, and sync incrementally by comparing stable file identifiers and checksums rather than re-reading folders.
• 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.

What Kord is not

Kord does not replace Egnyte and does not want to hold your files. Egnyte stays where documents live and where permissions are decided; Kord is the review and revision layer on top of it. Teams typically connect a handful of active project folders rather than the whole tenant.

Requirements

An Egnyte plan with API access, an API key from your Egnyte admin console, and a Kord account. 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 folder of yours.