Financial services document storage in Salesforce is a placement decision, not a feature toggle. Client statements, household agreements, KYC packets, and regulatory files can land on the wrong record, in a shared library, or in a tool nobody monitors. Knowing how to manage financial services document storage in Salesforce means deciding where each file type lives, who can open it, and what evidence you will accept before you sign. That review is the point of financial Salesforce consulting for firms that want the file design settled before a build starts.
Talk with Omnivo about a document storage review
A proposal that says "we will use Salesforce Files" has not answered the question. The useful review starts with the documents you already hold, the people who need them, and the records those files must stay attached to after go-live.
How to Manage Financial Services Document Storage in Salesforce
Start with an inventory, not a storage product. List the documents a firm actually keeps. Include new-account packages, IPS documents, custodial statements, tax forms, trust paperwork, and complaint files. Also list working notes an advisor should not file next to a client record. For each type, name the Salesforce record it belongs on and the person who may add, view, download, or remove it.
Salesforce gives you more than one place to put a file. Salesforce Files can sit on a record's Files related list, in a library, or in a user's private files. Classic Documents and old email attachments behave differently, and a file dropped into Chatter is not the same storage path as a file on an Account. A partner should say which path each document type will use, and why.
That map is the storage design. Without it, teams upload whatever is handy, and a later audit has to reconstruct intent from file names. Omnivo's financial services work starts from the operating model, including how portfolio, custodian, KYC, and document tools connect, before anyone treats a file feature as the plan. The same standard belongs in the statement of work.
Keep the inventory short enough to review in one working session. A useful row names the document and the record it hangs on. It also names the library, if any, and who can download it. Add how long the firm keeps it, and whether an outside system is the copy of record. If a row cannot be filled, that document type is not ready to migrate.
Where Should Client and Household Files Live?
Put a file on the record a reviewer will open. For many wealth and advisory firms, that is the household or the person account, not a generic shared folder and not an advisor's private files. A statement that only the uploading user can find is not stored for the firm. It is stored for that user.
Household and person-account designs change the question. A tax form may belong to one person, while an investment policy belongs to the household. If both files are dropped on whichever record was open, relationship teams and compliance will not see the same packet. Ask the partner to show one household with both kinds of files, using roles your firm actually has.
Libraries help when a file is not "owned" by one client record. Supervision samples, procedure manuals, and product files often belong in a library with named membership. They do not belong as attachments copied onto every household. Copying the same PDF onto hundreds of records inflates storage and leaves stale versions behind.
External document systems are a real option, not a failure. Portfolio tools, custodians, and dedicated stores often remain the system of record for large statements. Salesforce can still hold the link, the status, and the record of who reviewed the file. The risky design is a silent split: the CRM shows a file name, while the real PDF lives somewhere the access review never checks.

Before you accept an external store, ask three plain questions. Who can open the file without a Salesforce login? Does a change in Salesforce sharing also change access in that store? And which system will an examiner be shown first? If those answers are vague, the integration is not ready to scope.
Who Can See, Download, or Share a File?
A file's sharing is its own decision. Salesforce describes three broad visibility states: private to the owner, privately shared with specific people or groups, and visible to the company. A file posted to a public group or a public feed can become visible far beyond the team that uploaded it. Record access does not automatically mean the right file access, and the reverse is also true.
External users add a second test. A client or portal user who can open a record may also see files on that record unless those files are marked so they stay internal. A proposal for an advisor portal or a client site should say, file by file type, what an outside user can preview and what they can download. Turning on Experience Cloud is not that answer.
Download rights matter as much as view rights. A viewer who can download a tax packet can also email it outside the review you designed. Ask which roles may download, which may only preview, and who is allowed to create a public link. Salesforce also limits how many times a single file can be shared, so a design that shares one master file with every record can run into that ceiling. A library, or a controlled link pattern, is often the cleaner fix.
Owner and collaborator rights are easy to over-grant. The person who uploads a file can often upload a new version, edit details, change who has access, or delete it. In a financial firm, delete and "make private" should not sit with every advisor by default. Name the operations or compliance role that may remove a file, and the advisor role that may only add a version.
Broad admin permissions cut through ordinary sharing. Users with wide "view all" or "modify all" rights can reach files they do not own, with narrow exceptions such as private libraries. If your org already has several people with those rights, a tidy sharing rule on one object will not contain a sensitive file. Count those users before you treat the design as closed.
This is separate from the record-security model. Roles, profiles, and field access still matter, and they are covered in our guide to Salesforce data security for financial services. Use that review for platform controls. Use this one for the file itself: where it sits, who can take a copy, and how a share is revoked.
What Retention Evidence Should the File Design Produce?
Retention is a business rule you apply to a storage design. Salesforce will not decide how long your firm must keep a new-account form, a complaint file, or a marketing email. Your policies, your regulators, and your contracts do. The CRM design should make those rules visible: which files are in the retention set, who can delete them, and what remains after a person leaves the firm.
Version history is part of that evidence. A replaced IPS should not erase the prior signed copy. Ask whether each required document keeps prior versions, who can see them, and whether a delete removes one version or the whole file. If an outside store holds the PDF, ask whether its version history is what you will rely on, and how Salesforce points to the right version.
A file name is not a retention schedule. "Smith\_final\_v7.pdf" on a household record tells a reviewer nothing about the document type or the keep-until date. A small set of document categories, applied the same way on every household, is what makes a later sample possible. Our Salesforce data governance buyer guide covers ownership and definitions for the records themselves. The file categories should follow those definitions, not invent a second vocabulary.
Firms with FINRA obligations already have a harder retention question around books and records. That program is its own review, covered in our FINRA compliance buyer guide. This storage design should not pretend to be that program. It should show which Salesforce files are in scope for it, and which files stay in an archive outside the CRM.
Ask for a sample, not a policy paragraph. Pick ten households. Show the required documents and the version a reviewer would rely on. Show who can download them. Then show how someone would prove a file was not deleted early. If the sample takes a developer to assemble, the design will not survive an ordinary supervision week.
How Should Storage Capacity and Large Files Change the Scope?
File storage is a paid limit, and financial files consume it faster than contact records do. Scanned applications, quarterly statement packs, and image-heavy packets add up. A partner should estimate storage from your real file sizes and growth, not from a default org allocation copied into the proposal.
Size limits differ by where the file is uploaded. Salesforce's own file guidance says Salesforce Files can be as large as 10 GB in Files Home, in libraries, and on a record's Files related list. The same guidance keeps a 2 GB limit for files uploaded in Chatter posts and comments. Files larger than 2 GB download through the REST API or the download servlet, not through every screen a user might try. Classic Documents stay far smaller. A design that "just attaches the statement" can fail once real custodial files show up.
Those figures come from Salesforce's file size and sharing limits, and they can change by release and by edition. Treat them as a prompt for a written test, not as a promise that your org already has the headroom. Ask for the current file-storage used, the file-storage allocated, and the largest file your teams expect to store this year.
Large files also change the integration scope. A middleware job that pulls every statement into Salesforce may be the wrong spend if users only need to open the custodian's copy. Storing a link and a review status can be the better operating model, as long as access in the outside system is reviewed with the same seriousness. A consulting review should look at those connected tools before a firm pays to duplicate them inside the org.
Cleanup belongs in the same scope. Unused versions, files on inactive users, and copies left from a migration all count toward the limit. A partner who will "load history" should also say who will remove the duplicates, and how you will know storage is not drifting again six months later.
What Should a Partner Show Before You Sign?
Ask for a file design you can test with your own people. The minimum is a document-type map, a sharing model, a retention sample, a storage estimate, and a handoff that names who owns the files after launch. Omnivo staffs financial services work with senior consultants and prices the work on completed deliverables, so these artifacts should be deliverables, not slides.
| Review item | What good looks like | Weak answer |
|---|---|---|
| Document map. | Each file type names its record, library, and copy of record. | We will turn on Salesforce Files. |
| Sharing test. | Advisor, supervisor, and client roles are clicked through on one household. | Sharing follows the account. |
| External store. | Access changes and the audit trail are named in both systems. | The vendor is secure. |
| Retention sample. | Ten households show version, keeper, and delete rights. | A policy paragraph with no records. |
| Capacity. | Current usage, allocation, and this year's largest files. | A default limit pasted from a help page. |
| Handoff. | A named owner can add, review, and remove files without the partner. | We will train the team. |
Score the proposal against that table before you compare hourly rates. A cheaper build that leaves files on private user storage will cost more the first time a supervisor cannot produce a packet. A clearer build ties each document type to a record, a role, and a person who remains responsible.
The handoff should include the library membership, the sharing rules the partner changed, and a short note on how to reverse a bad share. It should also include the list of users with broad file-reaching admin rights. If that list is a surprise in week one after launch, it should have been a surprise during selection instead.
Portal and client-site scope needs its own line. If investors or plan sponsors will open files, the test must include those users, not only internal staff. Our notes on Experience Cloud portals for financial services cover the site decision. The file decision still has to say which packets a portal user can download.
Finally, ask what happens when an advisor leaves. Their private files, their draft uploads, and any public links they created should move to a firm owner or be closed. A design that keeps client PDFs in personal storage will fail that test even if every sharing rule looks right on paper.
A Practical Review Before You Approve the Build
You can run this review before a contract is signed. Give the partner five document types you actually use and one real household shape, with names removed. Ask them to place each file, name who can download it, and show what a supervisor would export. Then ask what they would refuse to store inside Salesforce, and where that file would live instead.
Listen for ownership. The right answer sounds like a working process. This file type sits on the household. Another stays with the custodian. One role can delete, and one report shows storage drift. The wrong answer sounds like a product list. Features do not manage documents. Decisions do.
Bring the same test to firms that already have an org. Inherited financial services orgs often hold years of stray attachments, private files, and library clutter. Cleaning that up is part of making Salesforce useful again, not a separate hobby. A storage review is often the fastest way to see whether the current org can be trusted with the next batch of client files.
If the partner cannot finish the sample in the sales process, do not assume the build will invent the discipline later. Placement, sharing, and retention get more expensive after thousands of files are already in the wrong place.
Call Omnivo to review your file design before you sign
Frequently Asked Questions
Does Salesforce include a full document management system?
Salesforce Files, libraries, and record attachments cover storage, versions, and sharing. They are not, by themselves, a retention program or a custodian archive. Many firms keep large statements in an external store and use Salesforce to show the link, the status, and who reviewed the file.
How large a file can we store on a client record?
Salesforce's current guidance allows files up to 10 GB in Files Home, libraries, and a record's Files related list, with a 2 GB limit in Chatter. Confirm the limit in your edition, and test the largest statement you actually receive. Also confirm users can download that file the way they work day to day.
Should we move every historical document into Salesforce?
Usually no. Move the files people must open on the client record, and link the rest if another system is the copy of record. Bulk-loading old PDFs spends storage and can duplicate stale versions. Ask for a keep, link, or leave decision on each document type.
Who should be allowed to delete a client file?
Keep delete, "make private," and public-link rights with a named operations or compliance role. Advisors can add a version without being able to erase the firm copy. Write that split into the sharing test you run before go-live.
How does this differ from a Salesforce security review?
A security review tests platform controls such as access, encryption, and audit evidence. A document-storage review tests where each file type lives, who can download it, and how long the firm keeps it. You want both, and they should not be the same workshop.

