Record files in Salesforce. Storage you own.

Galacia Vault connects a file component on Salesforce record pages to your customer-owned Amazon S3 storage.

See a file go from upload to preview.

Upload a text file from a Salesforce record, open its actions and preview its contents.

Screen recording of Galacia Vault in a Salesforce Developer Edition org, with sample data. 18 seconds.
Read the walkthrough
  1. Open Upload files from the Vault component on a Salesforce record.
  2. Select a file to upload to the connected storage. A confirmation appears when the upload completes.
  3. Open the file actions and choose Preview to read the text file within Salesforce.

Download the video or book a personalised demo.

Five things to look for on the record page.

Illustration of the Vault component with example data. Watch the walkthrough above for the product itself.
  1. Upload files

    The starting point. It opens the uploader with Browse Files and a drop zone, or Tap to Upload on mobile.

  2. Storage connection

    Shows where the file will go. Users check it before selecting a file.

  3. Folders and tags

    Where your setup offers them, users choose a folder and add tags during upload.

  4. File actions

    Each file row has an action menu. Download is there, and Preview appears where the file type and configuration support it.

  5. Upload limit

    The component shows the limit before a file is chosen. It may display the standard limit as about 1.4 MB, using binary units.

The file workflow, action by action.

Upload in the context of a record

Open the record, choose Upload files, check the storage destination and select your file. The completed upload appears against that record.

Follow the upload guide

Retrieve the file where you need it

Find the file on the record and choose Download from its action menu. Your browser handles the downloaded file.

Follow the download guide

Preview text files

In the standard S3 setup, text files can be previewed inline. PDFs are downloaded to view. An unavailable preview doesn’t mean the file can’t be downloaded.

Organise with folders and tags

Where offered in your setup, users choose a folder and add tags before selecting a file, and use filters to narrow the list.

Upload from mobile

On mobile, the uploader offers Tap to Upload. Check the limit shown in the component before selecting a large file.

Keep file permissions separate

Record visibility doesn’t grant file access. File sharing and storage-connection permissions get their own check.

How access works

What’s in, what’s out, and the limits.

These limits are defined in the product source. Confirm the configuration for your organisation during the demo.

Standard per-file limit
1.5 MB (1,500,000 bytes) per file on the standard Salesforce upload path. The component may display this as about 1.4 MB, using binary units.
Encryption at rest
On Amazon S3, Amazon’s server-side encryption applies on your bucket. Vault adds no encryption layer of its own on S3.
Larger files
Files above the applicable limit need separate technical qualification and configuration. They’re outside this standard assisted scope.
Storage
File contents use your agreed Amazon S3 bucket. Salesforce stores the file metadata and record association.
Permissions
Salesforce record visibility doesn’t automatically grant access to Vault files. File sharing and storage-connection permissions need their own check.
Organisation fit
Confirm your Salesforce edition, API access, record-page setup and connection configuration during the demo.
Not available
Future integrations and structured data storage are unavailable. Migration and larger-file transfer need separate scoping.

When to evaluate Vault, and when not to.

Evaluate Vault

Your users work on Salesforce records and your organisation wants customer-owned Amazon S3 storage behind that file workflow. You have an administrator and storage owner who can agree and maintain the configuration. Check the per-file limit above against the files your team normally uses.

Keep your current setup

If your existing Salesforce Files workflow already meets your access, storage and support needs, identify a concrete benefit before changing it. Compare the integration effort and full cost. Vault is not presented as an automatic saving or a universal replacement.

Compare the two approaches

Make the demo prove your workflow.

Bring a representative record, user roles and non-sensitive files. Ask to see an upload, a download checked against the original, and a restricted user denied access. Include your largest required file type and size in the scope discussion.

Agree the candidate version, test environment, file limits, acceptance checks and any evaluation charges before an assisted installation. A demo request does not create a trial or install software.

The record-page artwork on this website is an illustration. Use the walkthrough video and the assisted demo to inspect the product itself.