Stow, by GTM Cloud · Capture · Early access
A Salesforce required documents checklist, with every file in its place
Stow adds an upload area to any record page. People drop files and pick a category, and admins decide which documents are required and when they expire. Optional Document Reading can also read an invoice or a form into the fields you choose, for a person to check first.
You know this one
The auditor’s question is short: is the signed contract on file for this customer?
You open the account and scroll to Files. Scan_0043.pdf. Contract_final_v2.pdf. Untitled. A certificate that might still be valid, or might have lapsed in the spring. You open them one at a time, then email the account owner, who swears it was uploaded and says the original is in their inbox somewhere.
The standard Files list shows everything the same way. It can’t tell you what’s missing, or what’s about to run out.
A Salesforce required documents checklist that fills in as files arrive
To stow is to put each thing in its proper place. Stow does that for the files on a record. Users drop files, choose a category such as Invoice or Contract, and add a note, all in the same step.
Admins decide which categories exist and which are required, and set an expiry reminder for each. The record shows a checklist, for example 1 of 1 provided, and files nearing expiry are flagged. Files stay standard Salesforce Files. An optional reading feature goes further and reads an invoice or a form into the record, for a person to check first.
See it first. Take it back. Keep the receipt.
| Preview | Undo | Prove |
|---|---|---|
| Values read from a document appear beside it, with their source words, before they save. | A committed reading can be undone from Reading History. | A required documents checklist on the record, and a log of every reading. |
What you get
Every file categorized on arrival
Pick a category per file, or use Set Category for All for a batch. Suggestions based on the file name and type speed it up.
A checklist that shows what’s missing
Mark categories Required for the records they apply to. The record shows what’s provided and what isn’t.
Expiry reminders that reach the owner
Give a file an expiry date and its category a reminder lead time. Files nearing expiry are flagged, and the reminder goes to the owner.
Optional: read the document into the record
Document Reading reads PDF, image and Word files, such as invoices and forms, into the fields you choose. People check the values beside the document and commit them. Every change is logged and can be undone.
An agent can do the filing
With Agentforce and Flow actions, an agent can find a record’s files, read one and file it. It always previews and asks first.
How it works
- Enable objects. Choose where the uploader may run.
- Create categories. Add categories, their rules, limits and expiry reminders, and a reading rule if you want one.
- Place the uploader. Add the component to the record page in Lightning App Builder.
- Upload. People drop files, pick categories and add notes.
Two readers, two reasons
If you’re the admin
Manage a catalog of categories and the rules that offer them, by file name, type, size, record or person. Set allowed file types and a maximum size per category. No code.
If you’re the one signing off
Deals stall and audits hurt when nobody can say whether the signed contract is on file, or when the certificate runs out. Stow shows what’s in, what’s missing and what’s about to expire, on the record.
Today, and with Stow
| Today | With Stow |
|---|---|
| Files pile up with no sign of what they are | Every file categorized, with notes, in the same step as the upload |
| Invoice numbers and totals retyped from PDFs | Values read from the document, and checked by a person before they’re saved |
| Missing documents found only when someone asks | A required documents checklist on the record |
| Expiry dates tracked in a spreadsheet | Expiry flags and owner reminders on the file |
Where it’s strong, and what to know first
We’d rather you find the limits here than after you install.
Where Stow is strong
- Files are categorized in the same step as the upload, with suggestions from the file name and type
- A required documents checklist shows what’s missing at a glance
- Expiry dates with flags and reminders to the owner
- Files stay standard Salesforce Files, and category and notes are ready for reports, flows and Apex
- Optional Document Reading: values are proposed, a person commits them, and every change is logged
Good to know before you install
- Document Reading is optional and needs Einstein generative AI (Prompt Builder) turned on. The rest of Stow doesn’t.
- The Document Reading guides are in English for now.
- Files remain Salesforce Files, so your org’s file storage applies as usual.
- Stow collects and organizes documents. It doesn’t create them or collect signatures.
Questions people ask
How do I make a document required in Salesforce?
In Stow, an admin marks a category as Required for the records it applies to. Anyone who opens the record then sees a checklist of what’s provided and what’s missing, for example 1 of 1 provided. You also choose which objects the uploader runs on.
How do I track document expiry dates in Salesforce?
In Stow, you give a file an expiry date and give its category a reminder lead time. Files nearing expiry are flagged on the record, and reminders go to the owner. You set the lead time per category, so a certificate and an invoice can follow different schedules.
Are our files moved somewhere else?
No. They’re standard Salesforce Files and appear in the record’s Files list as usual. The category and notes are stored on the File itself, so reports, flows and Apex can use them, and your org’s file storage applies as usual.
Can a document trick the reader into writing the wrong field?
No. Only fields in your rule can be written, and text inside a file can’t name a field, an action or a category. A person commits the values unless you decide otherwise, and each value is shown with its source words first.
Do we need the reading feature to get value?
No. Categories, required documents and expiry reminders work without it, and without any AI feature turned on. Document Reading is optional, and it’s the one part that needs Einstein generative AI (Prompt Builder) turned on in your org. The checklist and reminders don’t depend on it.
Can an agent file documents for us?
Yes, with Agentforce and Flow actions. An agent can find a record’s files, read one and file it. The agent always previews and asks first, and it runs as the person it’s helping, so it can only reach what that person can.
Works well with
- Portage: the records are loaded. Stow collects the documents that belong on them.
- Pennant: put a notice on the page where people open the record.
Stow is part of the Capture stage of the lead-to-renewal map. Want help rolling it out across your objects? See our Salesforce services. Every app installs by itself. None needs another.
Built on the platform
- Three permission sets: Admin, User and Read Only.
- Document Reading proposes and your rules decide: only fields in your rule can be written, and everything is logged and undoable.
- Files reach the model only through the Einstein Trust Layer.
- In-app guides for administrators, users and Agentforce. The Document Reading guides are in English for now.
Bring an invoice and the record it belongs on
Ask for early access and a walk-through on the object where your teams collect documents. Drop a file, see the checklist update, and watch a document being read.