Questions buyers ask
before a demo.

Vault adds a file component to Salesforce record pages. People upload, find and download files there. The file contents are stored in an Amazon S3 bucket your organisation owns, and Salesforce keeps the file metadata and its association with the record.

On the Salesforce record pages agreed at setup, as the Galacia Vault File Manager component. If it’s missing for someone, an administrator checks the record-page assignment and that person’s permissions.

Upload it from the record, find it in the file list, download it from the row’s action menu and, where the file type and configuration allow, preview it. Folders, tags and filters are available where your setup offers them. See each action.

The uploader offers Tap to Upload on mobile. Check the upload limit shown in the component before choosing a large file.

Yes. An 18-second walkthrough with sample data shows a text file uploaded from a record, its actions and its preview. Watch the walkthrough.

In your own Amazon S3 bucket, in the region you agree at setup. Salesforce holds the file metadata and the link to the record. See what sits where.

The current assisted setup uses customer-owned Amazon S3. Any other provider would need separate scoping, so raise it in the demo.

In the standard S3 path, transfers go through Salesforce and the connection uses a Salesforce Named Credential for storage access. A separately configured transfer gateway is a different path and must be assessed if it’s included in your setup. Follow the file flow.

No. File sharing and storage-connection access are checked separately from Salesforce record access. They’re configured and tested during onboarding with both permitted and restricted users.

On Amazon S3, files are encrypted at rest by Amazon’s server-side encryption on your bucket. Vault adds no encryption layer of its own on S3. Discuss any further requirement in the demo and record the agreed configuration in your handover.

Your team. Agree who backs up file contents and Salesforce metadata, who tests restoration and how credentials are revoked. Owning the bucket isn’t a recovery plan on its own. See the responsibilities.

The file contents stay in your bucket. The file-to-record mappings live in Salesforce, so preserve them and check your team can retrieve the files it needs before removing the integration. Bucket access alone doesn’t rebuild those relationships. Agree the exit steps in your handover.

The standard upload path takes files up to 1.5 MB (1,500,000 bytes) each. Larger files need separate technical qualification and sit outside the standard assisted scope. Read the current scope.

Not automatically. If your existing Salesforce Files workflow meets your access, storage and support needs, find a concrete benefit before changing it. Compare the two approaches.

Migration needs separate scoping. Mention it in your demo request to start that discussion. It doesn’t confirm a migration service.

No. Future integrations and structured data storage are unavailable.

Start with a demo. Galacia then agrees a written offer with you covering storage, downloads, support and any migration scope. Payment follows that offer, through Stripe. A demo request doesn’t create a subscription or take payment.

Not today. There’s no self-service package installer, AppExchange listing or free trial. Galacia installs Vault with you after a demo and a written agreement, and handles the API connections, bucket configuration and testing. See how onboarding works.

Allow up to one working day once access and the agreed setup are ready. Confirm timing with Galacia before you plan a rollout.

Identify your Salesforce administrator and storage owner, a test environment, the record types you use and a few non-sensitive test files. Don’t send credentials or customer files through the demo form. Open the onboarding checklist.

No. It sends your details to James, who’ll contact you to arrange a time. No account or payment is needed, and no meeting slot is reserved.

Galacia publishes its support window, first-response target and who provides support on the support page. See support hours and response. Your written offer defines the support scope and any agreed commitments.

Start with your Salesforce administrator, who can check record access, the storage connection and the installed version. Read the access and errors guidance.