Skip to content

What Sliick Files does

Read this first if Sliick Files is new to you. It covers what your users see, where the files are actually stored, and the one decision an admin has to make before rolling it out.

Sliick Files puts a file list on the Salesforce record itself. From that list people can upload files of any type, preview them inline, tag them, search and sort, share them, and see the version history of each one. The same components work on record pages, app pages, and Experience Cloud pages, so people never leave Salesforce to find a document.

Every file has to live somewhere, and Sliick Files lets you choose. The storage provider is a single setting in Sliick Settings, and you can change it later.

OptionWhat it means
Salesforce FilesFiles stay in Salesforce and count against your Salesforce file storage.
Sliick Cloud StorageStorage Sliick operates for you. Nothing to create, no keys to manage.
Amazon S3 (and S3-compatible)Your own S3 bucket, or Backblaze B2, Wasabi, Cloudflare R2, or MinIO.
Azure Blob StorageYour own Azure storage account and container.
Google Cloud StorageYour own Google Cloud bucket.
SharePointA SharePoint site in your own Microsoft 365 tenant.

When you connect your own storage, files upload from the browser straight into your bucket, container or SharePoint site. Salesforce stays the gatekeeper that decides who can reach a file, but the bytes go directly between the browser and your storage.

  1. Install Sliick Files and assign the permission sets. See Install and permission sets.
  2. Add the file list to the record pages that need it. See Add the components to a record page.
  3. Decide whether to keep files in Salesforce Files or connect other storage. See Choosing a storage provider.
  4. If you connect other storage, set up the Integration User, then follow that provider’s section.

Nothing to install and nothing to log in to. The file list appears on the record, and Using Sliick Files covers everything you can do with it.

Sliick Files also ships a provider-agnostic file API you can call from Apex and Flow. File operations are written once and the bytes land in whichever provider the org has configured, with no provider name in the calling code. See Developer API.