Data residency

Read this before you enable the Image Processing Pipeline. It is the one setting that changes where your file bytes travel. Everything else in Sliick Files keeps bytes between the browser and your own container.

By default your file bytes travel browser to your Azure Blob container directly over SAS URLs. Salesforce is the access-control gatekeeper, but the bytes themselves never pass through Sliick-operated infrastructure.

There is one opt-in exception: the Image Processing Pipeline toggle in Sliick Settings. When enabled, newly uploaded image files are routed through Sliick’s processing service to perform HEIC to JPEG conversion, resizing, and thumbnail generation, and the processed image is then written back to your container. While processing:

• Only image content types are routed; non-image files (PDFs, docs, video) and all downloads never transit Sliick.
• The pipeline is off by default, and Sliick has to authorise your org before it can be enabled at all. It does nothing until an admin turns it on here.
• The hop is authenticated with a key unique to your org, and the service holds bytes only for as long as processing takes. It is not a durable store.

If your data-handling policy requires that image bytes never leave your own infrastructure, leave the pipeline disabled. Uploads still work: images are stored as-is, without server-side conversion or thumbnails.

Turning the pipeline on

Media processing is not configured in Salesforce Setup. You turn it on in the Media Processing section of Storage Settings and click Verify, after designating an Integration User. Your org also has to be authorised by Sliick first. The full steps, including the resize and quality settings, are in Media processing for images.