...
Dismiss local changes: Editors can make changes to content that has been pulled from a remote site. If the remote site pushes an update however, all local changes will be lost. Not recommended for most people as this can be confusing for editors.
Ignore updates completely: After a content item has been pulled, it will never be updated from changes on the source site and is completely decoupled. You can make any changes locally and they will persist.
Forbid local changes and update: Don’t allow editors to make any changes on content that was pulled from another site. Recommended for content staging and a general master-slave approach.
Update unless overridden locally: The best of both worlds. By default, changes from the source site will be pulled and replace the outdated content on the site. However, editors can explicitly override content to customize it- in this case the flagged content won’t be updated by remote changes and local changes will persist. See here for more details: Override content locally.
Create unpublished revisions: Only available for node bundles that are configured to create new revisions on every update. If set, pulled updates will always create a new unpublished revision, allowing your editors to review all changes per site before publishing them. You can use Drupal’s built-in and customizable review processes just as you would with locally created content.
Type and Field: File
Files are syndicated along with their file contents, so they are an exact replica as on the source site. If you don’t want to syndicate the same file to save storage, we recommend you use a CDN or DAM tool to manage these assets.
...