Galacia.

How it works

One upload.
Two places.

Vault keeps a file’s details on the Salesforce record and sends its contents to an Amazon S3 bucket your organisation owns. This page follows a file through the standard assisted setup.

The flow in 30 seconds

Watch one file make the trip.

A silent motion graphic of an upload from a Salesforce record to your storage, followed by a short clip of the real component.

Illustration with example data, then a screen recording with demo data. 30 seconds, no sound.
Read what the film shows
  1. The line “Files in Salesforce. Storage in your cloud.”
  2. A user drops a file called Site plan.png on the Vault component of an Account record.
  3. The file travels to a customer-owned bucket, such as Amazon S3.
  4. The record lists the file. A download fetches it from your storage.
  5. A clip of the real component, recorded in a Salesforce Developer Edition org with demo data.
  6. Vault is ready for onboarding: a demo, a written offer, then installation by Galacia.

The standard S3 path

Record page, Vault, your bucket.

  1. 01Salesforce record pageA user opens Vault on the record and asks to upload or download a file.
  2. 02Vault in SalesforceSalesforce code checks the file operation and the user’s connection access. File metadata and the record association stay in Salesforce.
  3. 03Your S3 storageFile contents use the agreed bucket and region. The standard connection uses a Salesforce Named Credential for storage access.
Illustration of the standard S3 path. Your agreed configuration is recorded at handover.

Step by step

Follow an upload.

These are the controls a user sees. Your administrator confirms the installed version, the storage connection and which actions are available.

Open the user guide

  1. Open the record

    A user opens the Salesforce record and finds the Vault component. If it’s missing, an administrator checks the record-page assignment and the user’s permissions.

  2. Choose Upload files

    They check the storage connection, pick a folder and add tags where those are offered, then use Browse Files, the drop zone or Tap to Upload on mobile.

  3. Vault checks and sends

    Code running in Salesforce checks the operation and the user’s access to the storage connection. The contents go to your bucket through a Salesforce Named Credential.

  4. The file appears on the record

    Salesforce holds the file’s metadata and its association with the record, so the file shows in the list for people who have access.

Step by step

Follow a download.

If a Preview action is available, it depends on the file type and configuration. In the standard S3 setup, text files preview inline and PDFs are downloaded to view.

Open the download guide

  1. Find the file on the record

    The user opens the same record and locates the file in Vault’s list, checking any active filters if it’s missing.

  2. Choose Download

    They open the file row’s action menu and choose Download. File sharing and storage-connection access decide whether the file can be retrieved.

  3. Check the result

    The browser handles the downloaded file. During onboarding, compare it with the original test file.

After the upload

What sits where.

Storage ownership is the point of Vault, so it helps to be exact about the split.

In your Salesforce org

The record keeps the context

  • The Vault component on your record pages
  • File metadata
  • The association between each file and its record
  • File sharing and storage-connection access

In your Amazon S3 bucket

The bucket keeps the contents

  • File contents
  • The region your team agreed
  • Retention and backup settings your team controls
  • Provider charges billed to your account

Access

A record is not a file-access grant.

Access to an Account, Case or other Salesforce record doesn’t automatically grant access to its Vault files. File sharing and storage-connection access are checked separately.

During onboarding, Galacia assigns administrator and user permissions and tests with both permitted and restricted users. A successful administrator test doesn’t prove the experience for everyone, so include the roles who’ll use Vault day to day.

Read the storage and trust notes

Transfer paths

The standard path and the gateway.

In the standard S3 path, transfers go through Salesforce. This is the path the assisted setup uses and the one the per-file limits describe.

A separately configured transfer gateway is a different path. It must be assessed if it’s included in your setup, and files above the standard limit need separate technical qualification.

Future integrations and structured data storage aren’t available. The Galacia website’s demo form is separate from this file workflow and never receives your Salesforce files.

Check your files fit

Know the size limit before the demo.

The standard upload path has a per-file limit. Bring your normal file sizes to the demo. Larger files and migration need separate qualification.

See current scope and file limits
Standard upload path
1.5 MBper file
Shown in the component as
1.4 MBapproximately, in binary units

See it with your own record types.

Bring a representative record, user roles and non-sensitive files. Ask to see an upload, a download and a restricted user denied access.

Book a demo