CtrlSync
CtrlSync is an M-Files vault application that keeps documents in step between an M-Files vault and SharePoint or Microsoft Teams. A vault administrator configures it; after that it runs on a schedule without anyone driving it.
The problem it solves is that people work where the conversation is. A project’s documents belong in M-Files, with its versioning and permissions, but the people editing them are in a Teams channel. CtrlSync lets both be true: a document lives in the vault, appears in the channel, and changes made in either place end up in the other.
Where to begin
Section titled “Where to begin”New to CtrlSyncConnections, what a sync cycle does, and what it deliberately does not do.
Installing itThe ordered path from an empty vault to a first synchronised library.
Looking up a settingEvery configuration setting, generated from the shipping application.
What is in this documentation
Section titled “What is in this documentation”| Section | What it holds | Written for |
|---|---|---|
| About | How synchronisation works, and its boundaries | Anyone evaluating or about to configure it |
| Set up | Entra registration, installation, vault structure — in order | The partner doing the deployment |
| Configuration | Reference for every setting | Whoever is editing the configuration |
| Examples | End-to-end walkthroughs in the sample vault | Anyone learning the product |
| Troubleshooting | Symptom, cause, fix | Administrators and support |
| Release notes | What changed in each version | Everyone |
Requirements at a glance
Section titled “Requirements at a glance”| Current version | 0.26.5.0 |
| Microsoft 365 | An Entra ID app registration with application permissions for Microsoft Graph |
| Licence | Per vault, applied as a .lic file |
| Other CtrlDocs products required | None |
For pricing and a trial, see CtrlSync on ctrldocs.com.