Two-way sync
Everything else in Sliick Files moves files one way: Salesforce writes, your storage holds. Two-way sync closes the loop, so a change someone makes directly in the bucket or the SharePoint library shows up on the Salesforce record. Read this before you wire it up for a provider.
Two-way sync is a premium feature. It is switched on for your org by Sliick. Until it is, the Sync section’s controls render disabled with a notice asking you to contact Sliick.
Which providers support it
Section titled “Which providers support it”| Provider | Supported | Wiring |
|---|---|---|
| Amazon S3 | Yes | Two-way sync on S3 |
| Google Cloud Storage | Yes | Two-way sync on Google Cloud Storage |
| Azure Blob Storage | Yes | Two-way sync on Azure |
| SharePoint | Yes | Two-way sync on SharePoint |
| S3-compatible providers such as Wasabi | No | No event notification service to point at |
| Salesforce Files, Sliick Cloud Storage | Not offered | The Sync section does not appear |
SharePoint connected in per-user (Delegated) mode cannot use two-way sync either. The toggle is disabled, because org-wide sync needs one fully privileged identity and per-user sign-ins cannot provide that. Viewing a record still keeps its file list current under the viewing user’s own access.
Turning it on
Section titled “Turning it on”- Connect your external provider and confirm the connection is Active.
- Do the provider-side wiring on the page for your provider above. SharePoint needs nothing here.
- Open the Sliick Admin app, go to Storage Settings, and select the Sync section in the left rail.
- Paste the identifier the page asks for, if your provider needs one.
- Turn on Enable two-way sync and click Save Sync Settings.
What syncs, and what does not
Section titled “What syncs, and what does not”- Adds and edits sync on every supported provider. A file replaced directly in storage becomes a new current version on the record.
- A brand-new file only syncs when it is in the right record’s folder, the same
{Record Name} - {Record ID}folder Sliick creates for its own uploads. A file dropped anywhere else is stored but not shown on any record until it is moved into a resolvable folder. - Deletes sync on SharePoint and Amazon S3. The file is removed from the record and parked in Deleted Files for an administrator to restore.
- External deletes do not sync on Google Cloud Storage or Azure Blob Storage. Both providers’ recommended delete-recovery settings, Object Versioning and blob soft delete, cause a delete to emit a different event than the one the notification listens for. A file removed directly in the bucket or container stays visible on its Salesforce record until someone removes it there too. Keep those settings on anyway: they are what makes an in-app delete recoverable.
- Enabling sync does not import files that were already sitting in your bucket. It applies to changes from that point on. SharePoint is the exception: turning sync on runs a one-time scan of the managed folder and picks up what is already there.
A console “rename” on Google Cloud Storage or Azure is really a copy plus a delete. The copy syncs in as a new file; the delete half does not sync, so the old entry stays on the record until you remove it in Salesforce.
How quickly changes appear
Section titled “How quickly changes appear”Within seconds in normal operation, and occasionally a couple of minutes. On Amazon S3, a freshly created notification configuration can take a while to start emitting reliably, so the first events after setup may lag. Press Refresh on a record’s file list for an immediate pull.