About CtrlSync
CtrlSync works from connection objects. Each one names a SharePoint site or a Teams channel, and says which documents in the vault belong to it. Everything else follows from that.
What a sync cycle does
Section titled “What a sync cycle does”On each run, for every active connection, CtrlSync asks Microsoft Graph what has changed since last time, brings new and modified files into the vault, and pushes vault changes the other way. Documents are matched by an identifier stored on the M-Files object, not by name, so renaming a file on either side does not create a duplicate.
Work happens in batches. Starting the job queues the next batch; at the end of a batch it queues another, until there is nothing left. That is why a large first synchronisation keeps going after the scheduled window has passed — it has not stalled, it is still working through the queue.
What it does not do
Section titled “What it does not do”- It is not a live sync. Changes move on a cycle, not the moment they happen. A very short interval strains the M-Files server without making the result meaningfully fresher.
- It does not co-author. Simultaneous editing of one document is CtrlShare, which is a different mechanism.
- It does not create Teams. Finding and creating teams and channels is CtrlTMS.
- It does not move permissions. M-Files permissions govern the vault copy; SharePoint permissions govern the SharePoint copy. Neither is derived from the other.