GalaciaUpload in the context of a record.
Open the record, choose Upload files in the Vault component, check the storage destination and select your file. Confirm the completed upload appears against the intended record.
Follow the upload guideProduct experience
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.
Read the walkthrough
- Open Upload files from the Vault component on a Salesforce record.
- Select a file to upload to the connected storage. A confirmation appears when the upload completes.
- Open the file actions and choose Preview to read the text file within Salesforce.
Retrieve the file where you need it.
Find the file on the record and choose Download from its action menu. File sharing and storage-connection access determine who can retrieve it.
Follow the download guideKeep storage responsibilities explicit.
File contents use your agreed cloud storage. Salesforce holds the file metadata and its record association. Galacia handles installation, connections, bucket configuration and testing; your team agrees access, region, retention and recovery.
See the storage flowCurrent assisted scope
The standard Salesforce upload path supports up to 1.5 MB (1,500,000 bytes) per file. With Galacia AES encryption enabled for the connection, the current limit is 1.125 MB (1,125,000 bytes) per file. Files above the applicable limit need separate technical qualification and configuration; they are outside this standard assisted scope. The component may display the standard limit as about 1.4 MB, using binary units.
Customer-owned storage
File contents use your agreed Amazon S3 bucket. Salesforce stores the file metadata and record association.
Permissions are separate
Salesforce record visibility does not automatically grant access to Vault files. File sharing and storage-connection permissions need their own check.
Confirm organisation fit
Confirm your Salesforce edition, API access, record-page setup and connection configuration for your organisation during the demo.
When 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.
When to 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.
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.
Future integrations and structured data storage are unavailable. Migration and larger-file transfer requirements need separate scoping. The website’s record-page artwork is an illustration; use the assisted demo to inspect the actual product.