Folders and breadcrumbs

Files in external storage are filed under a folder path. This page covers the two things you control: the root everything sits under, and the business folder path within it.

The folder hierarchy builder

Use the Folder Hierarchy Builder in Storage Settings to create and update folder templates per object, per provider, and optionally per record type, without leaving the Sliick admin page.

• Use the Active toggle to retire a template without deleting it. Inactive templates stay visible in setup for later reactivation, and new uploads ignore them.
• Updating a template affects new uploads only. Existing files stay at the storage path they were written to.

Sliick always preserves reserved path segments for the org, the object and the record. Your template controls only the business part of the path after that.

What users see

The file list and the image gallery show a friendly breadcrumb derived from the file’s stored path, so people see the business folder context without the raw provider path. It is display-only for them.

The storage root folder

Everything Sliick manages lives under a single root folder. The default is Salesforce-Files-<your org id>, which keeps each org and sandbox separate when they share a bucket. You can set your own, such as salesforce-files/ or acme-docs/, in Storage Settings.

Two rules apply to the value you enter:

• Letters, numbers, hyphens and underscores only, per /-separated segment. Spaces break the event filters that two-way sync depends on, and complicate URLs, so the setup UI rejects them.
• 50 characters maximum. The root is part of every file’s storage key, and that key has a fixed 255-character budget it shares with the record folder, a unique id and the file name.

A root folder saved with spaces before that rule existed keeps working, because only a changed value is validated. Turning on two-way sync for Amazon S3, Google Cloud Storage or Azure Blob Storage requires renaming it first: the sync save rejects a spaced root, because bucket event filters silently never match one.

Changing the root while two-way sync is on does not move the sync registration. Sliick warns you to update your provider-side filter to the new root and re-save your sync settings so it registers again.