Creating a Sync

To set up a Sync, choose a source and a destination from the folders within your site, on a Remote Server or Agent, or on a child site.

Any Site Administrator can add a new Sync to your site. Workspace Administrators can add Syncs within their Workspace.

Select options for how the Sync will be triggered.

Configure optional include and exclude patterns to control which files are affected by the Sync. You can also provide a human-readable description for the Sync to make sync management more convenient.

Who Can Create Syncs

Only users with admin-level access can create and manage Syncs.

Site Administrators can create and manage all Syncs. Workspace Administrators can create and manage Syncs for folders within their Workspace. Folder Administrators can create and manage Syncs for folders they control.

Source Folder

The source folder is where files are synchronized from.

The source folder can be a folder in the current site (including a Remote Server Mount folder), a folder on a Remote Server, a folder on an Agent, or a Workspace. Site Administrators can sync from any Workspace as the source; other users can only sync from Workspaces they have access to. Syncs created by a Site Administrator in a parent site can use a Child Site for the source folder.

Destination Folder

The destination folder is where files are synchronized to from the source folder.

The destination folder can be a folder in the current site (including a Remote Server Mount folder), a folder on a Remote Server, a folder on an Agent, or a Workspace. Site Administrators can sync to any Workspace as the destination; other users can only sync to Workspaces where they have write access. Syncs created by a Site Administrator in a parent site can target a Child Site for the destination folder.

When the Destination Folder Has Restrictive Folder Settings

When syncing files to a folder with folder settings that alter file contents or filenames (e.g. GPG Encryption, GPG Decryption, or Filename rewriting rules), you must enable the option to delete files from the source folder after copying.

To prevent repeatedly syncing the same files every time the process runs, your site will not start a sync to a destination folder that alters file contents or filenames. This prevents high transfer usage charges for a process that would offer no benefit to you.

After Copying

You can choose whether to delete or keep files in the source folder. Keeping files means the original files are retained in the source folder after they are copied to the destination.

Selecting delete removes copied items from the source folder, letting you clean up transferred files from the source location.

If you choose to delete, you can also Delete empty folders from the source when syncing. When syncing files from a source that creates uniquely named folders, we recommend enabling this feature so that your source folder does not accumulate unused empty folders.

End-Of-Sync Trigger Filename

Some Managed File Transfer (MFT) services require delivery of an empty file, known as a trigger file, to signal that data transfer is complete and further processing can begin.

Specifying a Trigger filename enables delivery of a zero-byte file to the sync destination once the sync has successfully finished.

The trigger file is the last file delivered, after all other files have been transferred.

The trigger file is only sent when files are transferred by the sync. If a sync contains no files, no trigger file is delivered.

Starting the Sync

Each sync can be configured to start automatically based on a schedule, started via an external trigger, started manually, or set to run on an automatic interval.

You can start a Dry run to simulate the results of a Sync without performing any file transfer or modification actions.

Automatic Interval type Syncs start running immediately when they are saved or enabled, unless the Sync is disabled or already running.