Sandbox install link
This will be the first link we publish. Use it in a sandbox only.
SOLUTIONS FOR CRM / INSTALL
Install Searchable Archive, sandbox first.
The managed package is not published yet, so there is no install link today. This page shows what you will need and how an evaluation runs. Until a package version exists, early access is assisted.
Install links
This package has not passed Salesforce security review
It is not an AppExchange-approved release. Install it only in a sandbox. Have your admin read the permission sets and the External Client App first, and keep it away from production data until you are comfortable. Details on Security.
Production install link
Not offered until sandbox results and the security review support it.
Until a package version exists, early access is assisted: we agree the scope with you, install the current build in your sandbox together and walk through the first scan. The inquiry form opens an email draft that you review and send yourself.
Before you start
A sandbox
Use a sandbox that holds a representative sample of closed Cases and their emails. Production comes later, after you trust the sandbox results.
Edition and API access
Salesforce Enterprise Edition or above with API access. That is the requirement on our pilot checklist today.
A Salesforce admin
Someone who can install a package, assign permission sets and approve the connection.
Your storage numbers
Setup → Storage Usage is the source of truth for Data and File Storage. Have your contract price per GB ready: the scan and the calculator both use it.
Managed Cloud only
A dedicated integration user, consent to the External Client App (OAuth with PKCE) and approval of the us-east-1 region.
Native only
File Storage headroom. Native snapshots are stored as Files, so they count against File Storage. The scan estimates how much.
In scope today: EmailMessage on closed Cases (the Cases stay in Salesforce) and flat custom objects after sandbox certification. Arbitrary object graphs and existing Files are not supported. See our limits.
Sandbox first, then decide
This is how an evaluation runs today.
- Install in a sandbox. When a link exists you will find it above. Until then we install the current build with you.
- Assign the permission sets below: ArchiveAdmin to your admins, ArchiveViewer to a few agents, and ArchiveIntegration to the integration user if you use Managed Cloud.
- Run the Get Started scan. It is read-only: it counts records, estimates size and shows an example saving. It does not copy or delete anything.
- Choose where the archive lives. Managed Cloud is the default. Native keeps it inside your org. Compare the data flows.
- Copy a small cohort first. The first run only copies. Check the copy, search for words inside email bodies, then read the results as a normal user and as someone who should not see them.
- Test restore against your own schema, required fields, automation and attachments before anything is removed.
- Only then consider source removal, on a small cohort. Two switches, one in the service and one in your Salesforce org, are off by default and both must be turned on. If anything looks wrong, pause the job and switch activation off. Archived copies stay.
The three permission sets
Assign the smallest set that does the job. Review each before you assign it.
| Permission set | Assign to | What it opens | Notes |
|---|---|---|---|
ArchiveViewer | Staff who need to find archived records. | The Archive Search tab and the viewer permission. | Results follow the user’s current access to the parent Case and the fields they can read. |
ArchiveAdmin | Admins who set up, run and approve archiving. | Archive Search, Archive Setup and the Get Started tab, with the viewer, admin and restore permissions. | Assign sparingly. Restore needs both the admin and the restore permission, and this set includes both. |
ArchiveIntegration | One dedicated integration user. Managed Cloud only. | Lets the service read the selected records and write restores. Includes Update Email Messages, so restored files link to sent emails. | Not for people. Grant it object and field permissions for the objects in your recipe, for example Case, EmailMessage, Task, EmailMessageRelation, Attachment, ContentVersion and ContentDocumentLink. The package does not open data permissions on its own. Review sharing as a non-admin user. |
Names are those of the source package. A managed package version may add a namespace prefix.
Install questions
Can I install Searchable Archive in production today?
No. There is no published install link, and the package has not passed Salesforce’s security review. Early access is assisted and starts in a sandbox.
Does the first scan change anything in my org?
No. The assessment is read-only. It counts records and estimates size across the objects the scanning user can access. It does not copy, archive or delete source records.
Do I need an AWS account?
No. Managed Cloud runs in our AWS account and Native runs inside your Salesforce org. Neither needs an AWS account of your own.
Which permission set does an ordinary agent need?
ArchiveViewer. It opens Archive Search, and what an agent sees still follows their current access to the parent Case and the fields they can read.
When will the install links be published?
We have not set a date. This page will show the links and the package version once a managed version exists and has been installed cleanly in a test org. Salesforce controls the timing of its own review.
Start with an assisted sandbox evaluation.
Tell us about your org and we will agree the scope, the storage mode and the first cohort. No Salesforce credentials are needed to ask.