Security model

Two design decisions govern access to files in Sliick Files. This page explains them so you can answer a security review without reading code.

Access follows the Salesforce record

The objects that hold file records and storage logs are Private. End users have no direct access to them at all. Everything goes through the Sliick Files components, which check the running user’s access to the parent record before returning anything.

In practice:

• End users work with files only through the file list, image gallery and profile photo components. If they cannot see the record, they cannot see its files.
• Administrators with the Sliick Files Admin permission set can view and manage the file and log records directly, for troubleshooting or cleanup.
• The Sliick Files User permission set grants access to the components only. It does not grant access to the file or storage log objects.

External storage does not widen this. Browser access to a file in your bucket uses a short-lived link generated only after Salesforce has checked the user’s record access, and the bucket itself is never publicly readable.

Deletion follows the file, not the current provider

When a file is deleted, Sliick deletes it from the provider that originally stored it, even if your org has since switched to a different provider. A file uploaded to Amazon S3 before you moved to SharePoint is still removed from Amazon S3.

This means a file is properly cleaned up regardless of your current configuration, and it is why the file list shows a provider badge on files that predate a switch.