This post defines the features we score for Salesforce document management apps, and how they add up. The shared method (the two axes, the confidence rules, Data Reliability and the Enterprise Readiness items) is in How We Compare Salesforce Document Apps. Everything below applies to document management only.
What counts as document management
An app belongs in this arena when its main job is managing files on Salesforce records: it connects each record to storage and lets people upload, find, open and organise files without leaving Salesforce. Neighbouring jobs, such as generating documents, reading them with AI, collecting signatures or sharing files outside the company with tracking, are scored in their own arenas. A product still gets credit for covering them, once, under Document stack coverage in Enterprise Readiness. Salesforce's own Files Connect is shown on the matrix as the baseline every app is measured against, not as a competitor.
Storage, file operations, permissions, metadata and sync in Salesforce.
Generation, document AI, e-signature and tracked external sharing.
Salesforce Files Connect: the reference point, not a rival.
How the Functionality score works here
Every product is rated on the same nineteen features. Each feature gets one rung on the five-rung ladder, from L1 Absent to L5 Extended, based on the public evidence we find. The Functionality score is the share of those nineteen features where the product reaches L4 Complete or L5 Extended.
The nineteen features fall into four groups. Storage Support covers which storage a product reaches, how deeply, and how people browse and search it. Basic Ops covers everyday file tasks such as upload, preview, rename and delete. Advanced Ops covers editing, versions, permissions, metadata and sync. Salesforce Support covers Classic, mobile and Experience Cloud.
Four features matter so much that a product is hard to use without them: connecting to the right storage, getting files in, getting them out, and respecting permissions. We check these first, and each must reach L4. A product that falls short is still placed on the matrix, and the gap is stated beside its score.
A product that misses one is still placed, and the gap is stated.
How the Automation score works here
Many teams want file work to run by itself when a record is created or changes. Ten features can be automated this way. We rate each on how far it runs through Flow, for admins, and Apex or an API, for developers, then average the ten into a separate score.
The features
Grouped into the four categories above. Each card gives the definition, the Kano class and why the feature has it, and whether automation is rated.
Storage Support
Storages Supported Kano · Dealbreaker
The external storage platforms a product can connect Salesforce to: SharePoint, OneDrive, Google Drive, AWS S3, Box, Dropbox and others. What matters first is whether the set covers the Microsoft, Google and Amazon ecosystems most customers run, which is Complete; reaching the other main platforms as well is Extended.
- L1 · AbsentNo connection to any external storage.
- L2 · WorkaroundOnly its own storage, or workarounds such as scheduled syncs or captured links.
- L3 · LimitedA limited set of storages that rules out a real share of customers.
- L4 · CompleteEnough storages for most customers, covering Microsoft, Google and Amazon.
- L5 · ExtendedMore than that, up to all the main storage platforms.
Why a Dealbreaker: A buyer whose files sit in an unsupported storage can't use the product at all.
Automation: rated on whether Flow and Apex can reach every storage the product supports.
Storage Depth Kano · Dial
How much of each storage's distinctive feature set the product exposes: SharePoint content types, term store and document sets; Google shared drives and labels; S3 storage classes and object tagging. Operations every storage shares don't count here.
- L1 · AbsentEvery storage treated as a generic file store.
- L2 · WorkaroundStorage-specific features reachable only in the storage's own interface.
- L3 · LimitedIn-app control of at least one storage-specific feature, on at least one storage.
- L4 · CompleteMost storage-specific features covered, for each storage supported.
- L5 · ExtendedFull coverage, plus capabilities the storage itself lacks.
Why a Dial: Each extra storage-specific capability adds value for the same customer, so more is steadily better.
Automation: rated on whether storage-specific features, such as creating sites or setting columns, can be driven from Flow and Apex.
Browse Library Kano · Delighter
Whether a user can move through the entire connected library from inside Salesforce, not only the files attached to the record in front of them, and which file and folder operations work while browsing. Saved views and bulk selection mark the top rung.
- L1 · AbsentNo way to browse external storage from Salesforce.
- L2 · WorkaroundA redirect to the storage, or another workaround.
- L3 · LimitedBrowsing, but limited in scope or features.
- L4 · CompleteFull browsing of the storage, with basic file and folder actions.
- L5 · ExtendedUseful extras such as saved views and bulk selection.
Why a Delighter: Record-level access covers most needs; a full library view is welcome but not expected.
Automation: not rated for this feature.
Search Kano · Dial
Whether external files and folders can be searched from inside Salesforce, and how far results can be narrowed (by tag, folder, property or sort order) rather than matched on filename alone.
- L1 · AbsentNo way to search files or folders through the app.
- L2 · WorkaroundCustom-built solutions, or redirects outside Salesforce.
- L3 · LimitedSearch works, but filtering or the results display is limited.
- L4 · CompleteEvery basic action on search results that the storage allows.
- L5 · ExtendedExtras such as tag-based search, folder-level filters and better sorting.
Why a Dial: Finding files gets steadily easier the more the search can filter.
Automation: rated on whether searches can run from Flow and Apex, and how precisely they can be targeted.
Basic Ops
Ingestion Kano · Dealbreaker
Uploading files and creating folders in the connected storage from Salesforce, and any limits on file size, type or destination along the way. Uploading whole folders or setting properties before upload are the extras at the top.
- L1 · AbsentCannot upload files or create folders through the app.
- L2 · WorkaroundOnly through code or third-party tools, such as the API, Apex or Zapier.
- L3 · LimitedSupported, with limits on size, type, features or destination.
- L4 · CompleteUploads and folder creation with no restrictions.
- L5 · ExtendedExtras such as folder upload and updates before upload.
Why a Dealbreaker: Without upload the product has no job to do.
Automation: rated on how much of uploading and folder creation can be driven from Flow and Apex.
Preview Kano · Delighter
Viewing a file's contents inside Salesforce without downloading it or opening the storage in another window. A redirect counts only as a workaround; an inline previewer with thumbnails and extra controls is the top rung.
- L1 · AbsentNo way to preview a file.
- L2 · WorkaroundA one-click download, or a redirect to the storage.
- L3 · LimitedOpens in another tab with limited navigation, or only some file types or sizes.
- L4 · CompletePreview inside Salesforce with basic navigation, for most file types and sizes.
- L5 · ExtendedExtras such as preloaded previews, thumbnails, inline preview and extra controls.
Why a Delighter: Users can always download instead, but viewing in place saves steps and stands out.
Automation: not rated for this feature.
Original Access Kano · Dial
Reaching the original file or folder in its storage from Salesforce, to open it in its native editor or work with it there, and how few clicks that takes. Choosing which editor opens, such as desktop Word or Word Online, is what the top rung adds.
- L1 · AbsentNo way to reach the original file or folder in storage.
- L2 · WorkaroundOnly by searching storage, copying links or clicking through several steps.
- L3 · LimitedOpens the file but not its folder, or only some file types or places.
- L4 · CompleteOpens the file in its native editor and its storage folder, in as few clicks as possible.
- L5 · ExtendedA choice of editor, desktop or online, and customisable clicks.
Why a Dial: Every click saved on the way to the source file makes daily work smoother.
Automation: not rated for this feature.
Download Kano · Dealbreaker
Getting files back out of the connected storage from inside Salesforce, for any file type and size. Bulk, folder and multi-select download are the extras at the top.
- L1 · AbsentNo way to download.
- L2 · WorkaroundA redirect to the storage, or several clicks to download.
- L3 · LimitedOnly some file types or sizes.
- L4 · CompleteAny file type or size.
- L5 · ExtendedBulk, folder and multi-select downloads.
Why a Dealbreaker: A file that can't be retrieved is of no use to the person who needs it.
Automation: not rated for this feature.
Rename Kano · Delighter
Renaming files and folders in their storage from inside Salesforce. Covering both files and folders is the bar for Complete; bulk or inline grid renaming lifts it further.
- L1 · AbsentNo way to rename files or folders from Salesforce.
- L2 · WorkaroundA redirect to the storage, or several clicks to rename.
- L3 · LimitedOnly files or only folders, no error handling, or limited types or places.
- L4 · CompleteFiles and folders, from inside Salesforce, with basic error handling.
- L5 · ExtendedBulk and inline renaming, with custom error handling.
Why a Delighter: Renaming is always possible in the storage itself, so doing it from Salesforce is a convenience.
Automation: rated on whether renames run from Flow and Apex.
Delete Kano · Delighter
Removing files and folders from the connected storage without leaving Salesforce, with basic handling of errors. Covering both files and folders is Complete; bulk or multi-select deletion is the step above.
- L1 · AbsentNo way to delete files or folders from Salesforce.
- L2 · WorkaroundA redirect to the storage, or several clicks to delete.
- L3 · LimitedOnly files or only folders, no error handling, or limited types or places.
- L4 · CompleteFiles and folders, from inside Salesforce, with basic error handling.
- L5 · ExtendedBulk and multi-select deletion, with custom error handling.
Why a Delighter: Clean-up can happen in the storage, so in-app deletion is a convenience rather than a requirement.
Automation: rated on whether deletes run from Flow and Apex, singly or in bulk.
Move / Copy Kano · Delighter
Moving or copying files and folders to a new place from inside Salesforce, with a choice of destination and basic handling of problems such as name conflicts. Every file and folder combination is needed for Complete; bulk actions and moves between two storages mark the top.
- L1 · AbsentNo way to move or copy from Salesforce.
- L2 · WorkaroundA redirect to the storage, or several clicks.
- L3 · LimitedOnly some combinations, such as moving files but not copying folders, or no choice of destination.
- L4 · CompleteEvery file and folder move and copy, with a choice of destination and basic error handling.
- L5 · ExtendedBulk actions, moves between storages, and custom error handling.
Why a Delighter: Reorganising usually happens in the storage, so doing it from Salesforce is a bonus.
Automation: rated on whether moves and copies run from Flow and Apex.
Advanced Ops
File Edit Kano · Delighter
Editing a file's contents from Salesforce. A button that hands the file to the storage's own editor counts for less than editing inside the Salesforce window, and a purpose-built editor or a choice of editor counts for most.
- L1 · AbsentNo way to reach an editable file from Salesforce.
- L2 · WorkaroundDownload, edit and re-upload, or edit in the storage yourself.
- L3 · LimitedAn edit button that only redirects to the storage's editor, or limited file types.
- L4 · CompleteEdit inside the Salesforce window, for most file types.
- L5 · ExtendedIts own editor with more than the native one offers, or a choice of editor.
Why a Delighter: Opening the file in its own editor already works, so editing inside Salesforce is a plus.
Automation: not rated for this feature.
Versioning Kano · Distractor
Seeing a file's version history from inside Salesforce and acting on it: opening, restoring or copying an earlier version.
- L1 · AbsentNo version control anywhere in the app.
- L2 · WorkaroundOnly by opening the original file in storage.
- L3 · LimitedA version button that only redirects, shows information you can't act on, or works for some file types.
- L4 · CompleteA version button showing the full history, with every version usable.
- L5 · ExtendedExtra controls such as restoring, versioned copies and version logs.
Why a Distractor: The storage keeps version history anyway, and buyers rarely ask to see it in Salesforce.
Automation: not rated for this feature.
Permissions Kano · Dealbreaker
Whether each Salesforce user sees and changes only what their own storage access allows, and how much of that access can be managed from the Salesforce side. Keeping Salesforce and storage permissions in sync automatically is the top rung.
- L1 · AbsentStorage permissions ignored in Salesforce, with no user-level control.
- L2 · WorkaroundEveryone sees files through one shared storage account; control only in storage.
- L3 · LimitedUser-level permissions, but only some combinations, read-only or write-only.
- L4 · CompleteFull user-level permission control for every file and folder, set by hand.
- L5 · ExtendedSalesforce and storage permissions kept in sync automatically.
Why a Dealbreaker: File access that ignores who the user is blocks most deployments.
Automation: rated on whether permissions can be granted and revoked from Flow and Apex.
Metadata Kano · Delighter
Reading and writing the properties stored alongside a file (SharePoint columns, tags and custom fields) within what each storage's API allows. Working around those API limits, mapping metadata, or setting it at upload are the extras at the top.
- L1 · AbsentNo file or folder metadata in the app.
- L2 · WorkaroundOnly by going to the storage.
- L3 · LimitedRead-only or write-only, core fields only, or limited file types.
- L4 · CompleteMost metadata readable, with some editing, within the storage's limits.
- L5 · ExtendedPast the storage's limits: more fields, mapping, and metadata set on upload.
Why a Delighter: Useful for tagging and routing, but most buyers can start without it.
Automation: rated on whether metadata can be read and written from Flow and Apex, and for which column types.
2-way sync Kano · Delighter
Keeping Salesforce and the storage in step, so a file added or changed on either side appears on the other, for files and folders alike. Instant sync, sync controls and logs mark the top rung.
- L1 · AbsentNo sync; files stay where they were uploaded.
- L2 · WorkaroundA manual re-upload or refresh to see changes.
- L3 · LimitedOne-way sync only, or limits on file size, type or method.
- L4 · CompleteTwo-way sync for all files and folders.
- L5 · ExtendedReal-time sync, with sync controls and logs.
Why a Delighter: A manual refresh gets by; sync that just works in both directions is noticed and valued.
Automation: not rated for this feature.
Salesforce Support
Experience Cloud Support Kano · Delighter
Whether external portal users (customers, partners, brokers, applicants) can work with files through Experience Cloud, and how much they can do. Upload, download and preview for every external user is Complete; editing, granular sharing controls, extra file and folder controls, branded sharing or analytics go further.
- L1 · AbsentInternal users only, with no external access.
- L2 · WorkaroundExternal users reached only outside Salesforce, through a public link or the storage's own portal.
- L3 · LimitedWorks in Experience Cloud, but external users get limited access, permissions or features, such as upload only, or each needs a storage licence.
- L4 · CompleteExternal users can upload, download and preview in Experience Cloud, with no storage licence needed.
- L5 · ExtendedBeyond the basics: editing, granular sharing controls, extra file and folder controls, branded sharing or analytics.
Why a Delighter: Buyers without portals handle external access another way, but it opens use cases the core job doesn't cover.
Automation: rated on whether files can be shared with and withdrawn from portal users through Flow and Apex.
Classic Support Kano · Distractor
Whether the product still works for orgs on Salesforce Classic, and with how much of its Lightning feature set. It answers a common RFP question even though few orgs still need it.
- L1 · AbsentLightning only; nothing appears in Classic.
- L2 · WorkaroundClassic users must leave Classic or switch to Lightning to reach files.
- L3 · LimitedA cut-down view, or only some components.
- L4 · CompleteFull feature parity in Classic, with documented setup.
- L5 · ExtendedParity kept across releases, plus use in custom Visualforce pages and buttons.
Why a Distractor: Almost every org now runs Lightning, so it rarely affects a decision.
Automation: not rated for this feature.
Mobile Compatibility Kano · Distractor
Whether the product works in the Salesforce mobile app on a layout built for phones, covering browse, preview, upload and share. Camera capture, offline access or mobile bulk actions are the top rung.
- L1 · AbsentNothing appears in the Salesforce mobile app.
- L2 · WorkaroundFiles reached only through the storage's own app or a browser.
- L3 · LimitedAppears but reduced: view and download only, or a layout not built for mobile.
- L4 · CompleteBrowse, preview, upload and share on a layout built for mobile.
- L5 · ExtendedMobile-only extras such as camera capture, offline access or bulk actions.
Why a Distractor: Very few customers ask for mobile file work, so it rarely changes a choice.
Automation: not rated for this feature.
When this list changes
Features are added or reclassified through the same Kano test, and every change is dated here. The current list of nineteen was set on 23 September 2026.