What this post is
This post compares 24Files and CloudFiles item by item on our published method: every score, where it came from, when we read it, and how much public evidence backs it. The verdict, with the composite scores, is on the comparison page; this is the working behind it.
| Published | Cycle | Arena |
|---|---|---|
| 29 September 2026 | Cycle 1 · sources read between 9 and 29 September 2026 | Document management for Salesforce |
→ See the verdict: 24Files vs CloudFiles
→ Every app in this arena, ranked on the same method
How we scored
Both products are scored on the same two-axis matrix, Enterprise Readiness (X) and Functionality (Y), with a Data Reliability check on the evidence itself. Items below carry a one-line summary; How We Compare Salesforce Document Apps sets out the method and defines each Enterprise Readiness item, and How We Score Salesforce Document Management Apps defines every feature. CloudFiles' own evidence for every item, on both axes, is compiled once in CloudFiles for Document Management: The Evidence; each CloudFiles box below gives the difference and cites its sources.
Enterprise Readiness Score (X)
How strongly each product is designed and sold for large organisations, and bought by them, scored 1–5 from four weighted signals. Unless an item names another source, the evidence comes from the vendors' own websites.
Observed buyers
Who actually buys each product, taken from evidence the vendors don't write themselves: the companies behind identified AppExchange reviewers, and the customers each vendor is willing to name.
AppExchange reviewer company sizes
The company size behind each identified AppExchange reviewer, as a read on who actually buys.
All 23 AppExchange reviews (all 5 stars, dated 2020-05-22 to 2026-03-04) were read from the listing's public reviews feed, and 16 reviewers were identified: 14 through the public Trailblazer profile attached to the review account, which states employer and role, and two by name against an employer's own page or the vendor's logo wall. Four are channel: a sales manager at a Belgian IT services firm that is a listed 24Files partner (501-1,000), a Salesforce consultant at a large Belgian consultancy (1,001-5,000), a developer at a Latin American Salesforce consultancy (51-200) and a consultant at a Swiss Salesforce partner (11-50). The 12 buyers span the range: a business operations manager at a UN agency and the manager of a large Canadian university's Salesforce services team (10,001+); a Salesforce DevOps lead at a New Zealand public insurer and a programme manager at a Belgian HR services group (1,001-10,000); a product owner at a UK telecoms infrastructure firm, an IT and security director at a Canadian electronics design firm, an applications and security manager at an Australian MS charity and a Salesforce administrator at a Belgian satellite-communications firm (201-1,000); an operations executive at a US wealth manager, an administrator at a US pump and water-equipment service firm and the owner of an executive-search firm (1-50); and one administrator at a US investment firm that could not be sized. By band, buyers are 1-50: 3; 51-200: 0; 201-1,000: 4; 1,001-10,000: 2; 10,001+: 2; unsized: 1. Seven reviewers could not be matched with confidence.
Buyers spread across every band from owner-run firms to a UN agency, in IT, platform and operations roles as well as admin roles, with no dominant profile; four of 11 sized buyers sit at 1,001+ staff, short of the 'most' that level 4 needs.
Fourteen of the 16 matches come from public Trailblazer profiles tied to the review accounts themselves, and four of those employers also appear on the vendor's logo wall; sizes are LinkedIn bands.
Last read on 2026-09-29Source – 1
One point higher: four of the seven identified CloudFiles reviewers work at organisations of 1,000+ employees, two of them at 10,001+.
The majority of reviewers who could be identified work at large organisations.
Identification is by public profile match, cross-checked on name, role and review date.
Last read on 2026-09-22Source – 1
Named customers: modal profile
The typical size and sector of the customers each vendor names publicly.
24Files has no case-study page: the site's page sitemap lists 10 pages and none is a customer story, and 24Flow's customer stories cover only its manufacturing platform. The named evidence is a wall of 16 logos on the Solutions and Pricing pages (seven rotate on the homepage), with no industry, date or outcome attached. Sized from public knowledge, seven are large or public-sector (House of HR, House of Talents, KERMI, Walo Bertschinger, the Australian Government Department of the Environment and Energy, the University of Toronto and ACC New Zealand), five are mid-size (WHP Telecoms, StenTech, AST Turbo, GARDP and HR&A Advisors), three are small (Journey Strategic Wealth, Stordahl Capital Management and TideRock Holdings) and one is unsized (Mentis Innovation). Sectors span HR services, construction, manufacturing, government, higher education, telecoms, consulting, finance and NGOs. The homepage also reproduces five AppExchange reviews as testimonials, one naming its organisation.
Mid-size to large organisations make up 12 of the 15 sized logos, with large and public-sector names the biggest single group, but they do not dominate and no case study backs any of them.
The logos are vendor-only and undated, but four of them are independently confirmed by AppExchange reviewers whose public profiles name those employers.
One point higher: all twenty of CloudFiles' named customers have an independently confirmed size, and fourteen are enterprise or regulated organisations.
A clear enterprise-modal profile.
Twenty sized names is enough to read a modal profile.
Where this leaves Observed buyers: CloudFiles reads more enterprise-ready on both signals: four of seven identified CloudFiles reviewers work at organisations of 1,000+, and enterprise or regulated organisations dominate its named customers. 24Files' identified buyers are spread across small, mid-size and large firms, and its named customers are a logo wall with no case studies.
| Metric | 24Files | CloudFiles |
|---|---|---|
| AppExchange reviewer company sizes | 3 · Mixed, High confidence | 4 · Leans high, Medium confidence |
| Named customers: modal profile | 4 · Leans high, Medium confidence | 5 · Highly ready, High confidence |
Commercial & service design
How each product is sold and served once a deal is signed: the billing unit and what the top tier gates, the support on offer, how buyers can try it first, and how visibly the vendor shows up at Salesforce events.
Pricing unit and tiers
How each product is billed, and what its highest tier holds back.
24Files is sold on yearly contracts in three tiers. User based costs €5 ($6) per user per month from 20 users; Mid-sized is a flat €5,000 ($6,000) a year for orgs of up to 250 users; and ORG based, for orgs above 250 users, is quote-only and adds a free onboarding session. The pricing page lists one feature set for all tiers, including Flow and Apex automation, multiple SharePoint sites, Experience Cloud and metadata sync, and the AppExchange listing presents its main features as available in any plan. Nonprofits get discounts, a 14-day trial is offered, and the terms invoice fees yearly in advance. The AppExchange listing carries the same per-user and organisation prices, and G2's vendor-supplied pricing matches ($1,199.99 for 20 users and $5,999.99 for 250 users a year).
The top tier for orgs above 250 users is quote-only, which meets the level-4 anchor, but it gates no API, automation or multi-site capability, so level 5 is not met.
The pricing page, the AppExchange listing, G2's vendor-supplied pricing and the terms agree on units, prices and billing.
Tied at Leans high: CloudFiles prices by quote, per org or per user, the sales-led model common in enterprise software.
Sales-led, quote-based pricing is the standard enterprise-software model, which reads Leans high.
Licensing terms are stated on CloudFiles' pricing pages; prices are set by quote.
Customer support
The channels a customer can use to reach help, and what each vendor commits to.
Support is by email. The terms say 24Flow provides product support through support@24files.eu for reporting product issues and is never responsible for customer-specific configuration services, and the docs' Support link opens an email. A docs page explains how to grant 24Flow Support login access for troubleshooting, with a one-month minimum for technical escalations. The AppExchange listing gives the support address and points to the knowledge base and video gallery, with its SLA, 24x7 and premium-support flags all off; its description says responsive support is included in every plan. No live chat, support phone line, response-time commitment or support tier is published on 24files.eu, and a free onboarding session is named only for the quote-only tier above 250 users. Reviewers consistently praise fast, hands-on help, including a feature built on request.
Help comes by email plus a strong self-help library, with no published real-time channel and onboarding only in the top tier; nothing is sold as an add-on, but configuration help is excluded from support altogether.
Confidence is not rated for this item; the score rests on the terms, the AppExchange support fields, the docs and the pricing page.
Three points higher: CloudFiles includes all its support free with every paid plan (live chat, email, and as many live calls with a solution engineer as the implementation needs, including help with Flow, Apex and the API), with nothing sold as an add-on.
Real-time and scheduled help, all included in every plan with nothing sold as an add-on, is the rubric's high case.
Support terms are stated on CloudFiles' own pages and confirmed in customer reviews, with no figure to check, so Confidence isn't scored.
Conference and webinar presence
Where each vendor appears in the Salesforce event calendar, and at what level.
24Files has no events of its own. Its vendor 24Flow runs product release webinars on Livestorm that include a 24Files segment: the Spring '26 Technical Deep Dive on 1 April 2026 (new Apex actions to list a SharePoint folder's contents) and the Summer '26 Technical Deep Dive on 2 September 2026 (working without a public folder and extended SharePoint metadata support). 24Flow's other three listed webinars (October 2025 to June 2026) and all seven trade shows it lists for 2025 and 2026 (Hannover Messe twice, Smart Manufacturing Week, ESEF Maakindustrie, ABISS in Belgium and the Netherlands, and Vision, Robotics & Motion) cover its manufacturing platform. No Trailblazer Community or regional Salesforce event was found, and neither 24Files nor 24Flow is among the 240 sponsors in Salesforce's Dreamforce 2026 directory.
The only 24Files presence is a segment in two self-hosted vendor release webinars in 2026, which is occasional self-hosted webinars.
Confidence rests on how many events are found: two dated vendor webinars with 24Files content, in April and September 2026.
Three points higher: CloudFiles has exhibited at six Salesforce flagship events in two years, including Dreamforce 2024 to 2026 and three World Tours.
Repeated flagship sponsorships with booths and theatre sessions are the rule's high case.
Six flagship events found across two years, with booth and session detail for five and one confirmed by Salesforce's own Dreamforce account.
Hands-on evaluation
How a buyer can try each product before committing.
24Files offers a self-serve free trial. The homepage FAQ says a trial can be started straight from AppExchange, the listing promises a 14-day trial with full functionality, and the listed package installs into the buyer's own org on a 14-day trial licence for 10 seats. The docs explain installing into a sandbox through the vendor's install page by choosing Try it Free. The AppExchange Test Drive is disabled. Buyers can also watch a 19-minute setup and demo video or book a live demo through a scheduling link on the homepage and pricing page. Setup needs a Microsoft Azure app registration before anything works, and no guide to what to try during the trial is published.
A self-serve, full-function free trial exists, but it installs in the buyer's org and needs Azure setup, with no no-install Test Drive or evaluation guide.
The trial is stated on the listing, homepage and pricing page and matches the package's trial settings in the AppExchange listing data.
One point higher: a Try It button on every CloudFiles AppExchange listing opens a pre-configured test drive org with nothing to install, and CloudFiles documents a guided test drive for each product.
A documented, no-install test drive with a guide for each product is the rubric's high case.
The test drive opens from the AppExchange listing and is documented in CloudFiles' help centre.
Where this leaves Commercial & service design: The two tie on pricing, each reading Leans high. CloudFiles leads on support, hands-on evaluation and events: all its help is included in every paid plan, where 24Files' terms offer support by email for product issues only; its test drive needs no installation, where 24Files' trial installs in the buyer's own org; and it exhibits at Salesforce's flagship events, where 24Files appears in its vendor's release webinars.
| Metric | 24Files | CloudFiles |
|---|---|---|
| Pricing unit and tiers | 4 · Leans high, High confidence | 4 · Leans high, Medium confidence |
| Customer support | 2 · Leans low, confidence not scored | 5 · Highly ready, confidence not scored |
| Conference and webinar presence | 2 · Leans low, Medium confidence | 5 · Highly ready, High confidence |
| Hands-on evaluation | 4 · Leans high, High confidence | 5 · Highly ready, High confidence |
Technical design
What each product is built to sell into, read from its compliance claims and what backs them, the depth of its public documentation, and its developer access.
Security & Compliances
The certifications each vendor claims, and whether anything outside its own word backs them.
24Files claims no certification. Its docs security page states that 24Flow does not keep a standalone SOC 2 report and argues none is needed because the managed package runs inside Salesforce, stores no customer data and hosts no service, pointing instead to the certifications Salesforce and Microsoft hold. The same page names controls: OAuth sign-in with no stored SharePoint credentials, role-based access with admin, user and community-user roles, permissions inherited from SharePoint, minimum SharePoint API permissions, and code and dependency scanning with Checkmarx and Snyk. The AppExchange listing records a passed security review (approved 24 December 2024 for version 5.60.0) and calls the app GDPR compliant, and the terms commit both parties to the GDPR. The terms mention a data processing agreement where applicable, but none is published, and no sub-processor list, ISO 27001, HIPAA, residency option or trust portal was found.
No certification is claimed, but the docs describe access controls specifically, which meets the level-3 anchor; nothing approaches the several certifications of level 4.
The controls are stated clearly in vendor docs; only the AppExchange security review can be checked outside the vendor's own pages.
Two points higher: CloudFiles is independently audited for SOC 2 Type II and holds ISO 27001, 27017 and 27018 certification and HIPAA compliance with BAAs, backed by a public GDPR DPA and a Trust Portal.
An audited SOC 2 Type II report, ISO and HIPAA certification, a public DPA and a Trust Portal together meet the rule's high bar.
The public DPA and Trust Portal let buyers check these claims, and the SOC 2 Type II report is shared under NDA, as is standard.
Help-doc architecture
How complete and searchable each vendor's public documentation is.
The 24Files manual at docs.24files.eu is a Confluence-based help centre with site search; its sitemap lists 85 pages (84 articles plus the home page), most recently modified on 9 September 2026. Sections cover setup (domain, remote site settings, Lightning Web Security, SLDS 2 and an eight-page Azure and Graph API app-registration section), administration (settings, object configuration, folder structures, 360 View, email-to-case, permissions and licence assignment), the Lightning component (including mobile, global search, Copilot search and Field Service Mobile), multi-language use, automation (eight Flow how-to pages, platform events and an Apex method reference), upgrades, errors and troubleshooting, a security page, a knowledge base, an FAQ and 11 seasonal release-note pages from Spring '23 to Winter '27. The website adds 11 tutorial videos and a six-question FAQ.
Setup, administration, security, developer reference and release notes are all covered in an organised, searchable manual.
The page count comes from the docs' own sitemap, and each area was opened and read today.
Tied at Highly ready: CloudFiles' help centre spans 492 indexed pages across setup, administration, security, developer reference and release notes.
Every documentation area the rule looks for is covered, and the page count is the highest measured.
An exact page count, taken from the published sitemap and index.
API depth and gating
The REST API and Apex client each vendor offers developers, and any pricing gate on them.
24Files has no public REST API, webhook or SDK: it is a managed package that hosts no service, so its integration surface runs inside Salesforce. That surface is well documented. An Apex methods page covers 18 global methods in the sfy_office365 namespace (folder and folder-structure creation, single and bulk upload, file links, metadata sync and upload, record-folder rename, folder path, move, file and folder removal, batch migration from Salesforce storage, Chatter file links and file listing), with parameters, authenticated and anonymous modes, a 35 MB per-file limit and chunking guidance of about 40 records. Two platform events (file uploaded, and a generic async-completion event) carry documented fields, and eight Flow how-to pages use the methods as invocable actions. The listing and pricing page include Flow and Apex automation in every plan.
One of the two: an Apex client with a real reference, but no public API.
The Apex reference is precise and corroborated by the listing and the homepage FAQ, and the vendor states it hosts no service, which rules out an external API.
Two points higher: CloudFiles publishes a REST API and an Apex client, ungated on every plan.
A REST API and an Apex client, open on every plan, is exactly what the rule scores highest.
The endpoint and method counts are CloudFiles' own published figures.
Where this leaves Technical design: The two tie on documentation, each with a full, searchable help centre. CloudFiles leads on security and developer access: it is independently audited for SOC 2 Type II and publishes a REST API and an Apex client, where 24Files keeps no standalone SOC 2 report and offers Apex methods with no REST API.
| Metric | 24Files | CloudFiles |
|---|---|---|
| Security & Compliances | 3 · Mixed, Medium confidence | 5 · Highly ready, High confidence |
| Help-doc architecture | 5 · Highly ready, High confidence | 5 · Highly ready, High confidence |
| API depth and gating | 3 · Mixed, High confidence | 5 · Highly ready, High confidence |
Messaging & ecosystem
Who each vendor says it serves and how far that claim travels beyond its own site: messaging focus, named partners, the make-up of its team, and its footprint on review platforms.
Stated ICP and messaging focus
Who each vendor's marketing says the product is for, and how narrow that pitch is.
The homepage headline is horizontal ('Salesforce & SharePoint Online Integration'), with saving Salesforce storage costs among its main claims. The Solutions page names six industries (finance and insurance, consulting and HR, government, NGOs, pharma and manufacturing) with no named customer per industry, and opens on regulated firms and the public sector. The pricing page runs from 'small teams and organisations' to enterprises above 250 users, and the tutorials address Salesforce admins and IT architects. The AppExchange listing targets horizontal, engineering and construction, and financial services industries, admin, business-user and sales personas, and the Sales, Service and Financial Services clouds. Recent 24Files YouTube descriptions frame the product for discrete-manufacturing and make-to-order firms, the market of 24Flow's main platform.
Messaging spreads across segment types, from small teams to enterprises and from NGOs to regulated industries, with no single enterprise or IT-buyer focus.
The vendor site, the AppExchange listing and the vendor's videos agree.
One point higher: CloudFiles' Salesforce pages are aimed at enterprise teams in regulated industries, such as financial services, healthcare and the public sector, and at their IT and security teams.
Messaging leans towards enterprise buyers in regulated industries and their IT and security teams, with broader industry pages alongside.
The buyer, industries and use cases are named precisely on CloudFiles' Salesforce pages.
Partner ecosystem
The integrators and consultancies each vendor names as partners, and whether they confirm it.
24Files runs a partner programme for Salesforce system integrators (page published January 2024, last modified 4 November 2025) offering partner training and referral commercial options through a contact form, with no tiers, requirements or directory. Its 'Our Partners' wall shows four logos: Easi, a Belgian IT services firm (501-1,000); Inetum-Realdolmen, the Benelux arm of the Inetum group; Stellar Solutions; and an unlabelled cartoon-mascot logo that could not be identified. No partner's own site or channel was found to mention 24Files. The only outside trace is a January 2025 AppExchange review of 24Files by a sales manager at Easi.
A programme page with named logos but no partner-confirmed relationship; the Easi review shows use, not a stated partnership.
The programme page is clear, but the absence of partner confirmation is a searched negative.
Two points higher: CloudFiles' partner page names nine implementation partners and six global integrators it has delivered customer projects with, and an IT consultancy names CloudFiles as a partner on its own channels.
A formal programme with nine named implementation partners, plus delivery with global integrators, reads Leans high.
One partner confirms the relationship on its own channels, and CloudFiles' partner page names nine implementation partners and six global integrators.
Team mix
The spread of sales, success and support roles on each vendor's LinkedIn page, and the regions covered.
24Files is a LinkedIn showcase page of 24Flow with 2-10 employees and 66 followers, and a showcase page has no people breakdown. 24Flow's own page shows 11-50 employees, 17 associated members and 1,978 followers, founded in 2021 with a single location in Ghent; the AppExchange publisher record gives 15 employees. The logged-in People read of 2026-09-21 found Engineering 8, Business Development 4, Marketing 2, Finance 1 and IT 1 as the top functions, with no customer success or support function, and 24Flow positions itself as a manufacturing shop-floor platform, so that go-to-market team serves its main product first. Reviewers most often credit a small, responsive support and development team, and the founder answers reviews personally.
Business development is the only go-to-market function visible, thinly and mainly for another product, and customer success and support do not surface, all in one region.
LinkedIn function counts are floors shared with 24Flow's manufacturing platform and were last read with a logged-in session on 2026-09-21.
Three points higher: CloudFiles' team combines an even mix of business and technical roles with coverage across time zones.
A strong, even mix of business and technical roles, spread across time zones for round-the-clock coverage.
The function mix and regions are read from CloudFiles' LinkedIn page.
Review-site profile richness
How complete each vendor's G2, Capterra and TrustRadius profiles are.
G2 has a 24Files profile listed 'By Scalefactory.eu' with a 'Re-claim Profile' prompt, so the vendor does not currently hold it. It carries an overview written by a 24Flow co-founder, vendor-supplied pricing for three tiers, three product images, one category (Salesforce AppExchange Apps) and two reviews averaging 4.8, one of them from a reviewer whose name and initial match that co-founder. Capterra has a fuller profile with provider data verified: 15 features, four integrations, a three-tier pricing table, support and training options, alternatives and one 5.0 review, from the vendor's own managing director. TrustRadius has no 24Files profile. The product's other 23 reviews sit on AppExchange.
One well-populated profile (Capterra) and one thin, unclaimed one (G2), with nothing on TrustRadius.
Confidence is not rated for this item; the score rests on the G2 and Capterra profile reads and a dated TrustRadius search.
One point higher: CloudFiles has profiles on G2, Capterra and TrustRadius, led by a claimed G2 profile with 227 reviews and a product video.
Profiles on all three sites, led by a rich, actively maintained G2 profile.
This item counts where CloudFiles has a profile rather than grading a claim, so neither Precision nor Corroboration applies.
Where this leaves Messaging & ecosystem: CloudFiles leads on all four: messaging aimed at enterprise buyers in regulated industries, a formal partner programme with named partners, a team spread across time zones, and review-site presence, where 24Files' Capterra profile's only review is by its own managing director.
| Metric | 24Files | CloudFiles |
|---|---|---|
| Stated ICP and messaging focus | 3 · Mixed, High confidence | 4 · Leans high, High confidence |
| Partner ecosystem | 2 · Leans low, Medium confidence | 4 · Leans high, Medium confidence |
| Team mix | 2 · Leans low, Medium confidence | 5 · Highly ready, High confidence |
| Review-site profile richness | 3 · Mixed, confidence not scored | 4 · Leans high, confidence not scored |
Features Score (Y)
How complete each product is across the feature map's four scored categories, each feature rated on a five-rung ladder from Absent to Extended, with Dealbreaker features able to gate the whole score: each must reach L4. The score itself is the average rung across the eighteen features, weighted by Kano class (Dial 3, Delighter 2, Dealbreaker 1, Distractor 0), on a 1–5 scale. Each card gives the rung and why the evidence lands there, the feature's Kano class and, where it applies, an automation rating.
Storage Support
The storage behind each product: how far it reaches into the storage's own features, and how easily a user can browse and search what's stored there.
Storage Depth Kano · Dial
Control over storage-specific features, beyond what every storage shares.
24Files lets admins choose a SharePoint site and document library per object or record type, route a single record to its own site (for example a Microsoft Teams team's site) through a record field, a Flow or the user's own choice, and make the document library itself the record folder. The component shows SharePoint library columns chosen from a weblist and writes column values at upload, applying SharePoint's mandatory and multi-select settings. The docs state that managed metadata (term store), person or group, hyperlink and lookup columns cannot be written through the Graph API, that subsites, hub sites and /teams/ site paths are not supported, and they do not mention content types or document sets. An unlisted vendor video from May 2026 shows the same component connected to Google Drive (My Drive, with the presenter saying a shared drive also works).
Per-record site routing and writing SharePoint library columns from Salesforce are in-app control of SharePoint-specific features, which meets Limited; term store, content types and document sets are not covered, so most SharePoint-specific features are not, and Complete is not met.
Upload Metadata and Metadata Sync write SharePoint columns and run from Flow (as Apex actions) and from Apex, and the docs describe a Flow filling the per-record site field, but no action creates sites or libraries, content types or managed metadata.
One rung higher: CloudFiles controls most SharePoint-specific features from Salesforce (sites, drives and Microsoft Teams from templates, six column types and their defaults, property search and SharePoint events), plus Google Drive shared drives and S3 bucket prefixes with automatic sync.
Most of SharePoint's storage-specific features are controlled from Salesforce, with specific controls on Google Drive and S3 too, which is Complete.
SharePoint sites and drives can be created from templates, with design, language, admins and column defaults, from Flow or Apex, well beyond editing what already exists.
Browse Library Kano · Delighter
Browsing the whole storage library from Salesforce, not just one record's files.
When a record page loads, the 24Files component lists the SharePoint folders and files in that record's folder, and users with authenticated access can open subfolders, return through a breadcrumb, create folders and act on items through per-row menus: preview, edit, rename, delete, move, download and copy public link for files, and delete, move and rename for folders. Admins can make the document library itself the record folder, which opens the whole library in the component, and 360 View shows the folders of child or junction-linked records on a parent record. Anonymous users see only the record's Public folder. Saved views and bulk selection are not documented.
Users browse the full record-folder tree, or the whole library when it is set as the record folder, with basic file and folder actions inside Salesforce, which meets Complete; no saved views or bulk selection are documented for Extended.
Browsing the library is something a person does on screen, so there is no automated version of it to rate.
One rung higher: a standalone Content Library tab browses six storage providers with nested folders, and List Actions add checkbox-based bulk selection on top of the same file operations.
Browsing with file and folder operations covers Complete, and checkbox bulk selection is the extra that takes it to Extended.
Browsing happens on screen, so there's nothing here for a flow or code to do.
Search Kano · Dial
Finding external files from Salesforce, and how far the results can be filtered.
24Files offers two search routes inside Salesforce. Global Search finds SharePoint files through 24Files Chatter File Link records, which exist only for files in folders that have been opened in the component, uploaded through it or processed by an Apex action, and admins can choose the fields shown in results. Copilot Search, added in the Winter '27 release, puts an icon in the component that runs natural-language queries through the Microsoft 365 Copilot Retrieval API across document titles and content in the record folder, and returns text snippets with View in 24Files, download and open-in-SharePoint actions for each result; it needs a Microsoft 365 Copilot licence and activation on the org by 24Files. The Google Drive preview video also shows a 'Search inside Google Drive' keyword box in the component.
Search runs inside Salesforce with open, download and view actions on results, which meets Complete, and Copilot's natural-language search of document content within the record folder is an extra beyond filename matching, which meets Extended.
The List Files in Record or its Folder action runs from Flow and Apex and returns a record's files (whole tree or one folder) with name, type, size and last-modified details, but it takes no keyword, metadata or content query, so targeting is thin.
Tied at Extended: beyond a sub-folder-aware search bar, a documented Flow action searches by resource metadata, filtering results by tag rather than filename alone.
Tag and metadata filters go beyond keyword matching, which is what earns the top rung.
Keyword and metadata search both run from Flow and Apex, and the REST API searches across twelve storages.
Where this leaves Storage Support: The two tie on search at Extended. CloudFiles leads on storage depth and browsing: Flow and Apex create SharePoint sites, drives and Teams and set columns, and a Content Library tab browses the whole library with bulk selection, where 24Files assigns sites per object or record and browses from the record folder.
| Feature | Kano | 24Files rung | CloudFiles rung |
|---|---|---|---|
| Storage Depth | Dial | L3 · Limited | L4 · Complete |
| Browse Library | Delighter | L4 · Complete | L5 · Extended |
| Search | Dial | L5 · Extended | L5 · Extended |
Basic Ops
The everyday operations a user expects to run on stored files without leaving Salesforce: uploading and downloading, previewing, opening the original, and renaming, deleting, moving and copying.
Ingestion Kano · Dealbreaker
Getting files and folders from Salesforce into storage, and any limits on the way.
Users upload files by dragging them onto the component or through Upload Files, create folders from the component, and can be asked to fill in SharePoint columns at upload. The docs state that file size is limited only by SharePoint's APIs and should be at least 2 GB, and an AppExchange reviewer reports customers uploading log files over 500 MB through a portal. Folder structures are created when a record page first loads, from admin-defined templates with record-field names and filter rules, and files added to Salesforce Files, Notes & Attachments or logged emails (including Email-to-Case) can be moved to SharePoint automatically, optionally deleting the Salesforce copy. A duplicate-name setting replaces, renames or blocks the upload. Uploads through Apex and Flow are capped at 35 MB per file.
Uploads and folder creation work inside Salesforce with no vendor-stated size, type or destination limit for manual uploads, which meets Complete; no folder upload is documented, and entering metadata at upload is the only pre-upload step, which on its own does not lift the rung.
Flow and Apex actions create single folders, lists of folders and whole folder structures and upload single or batched files, with anonymous-mode targets, delete-after-upload, extension filters for batch migration and success or failure platform events, which goes beyond the basics.
Last read on 2026-09-29Sources – 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
One rung higher: whole-folder drag-and-drop upload is backed by dedicated batch and async Flow automation, beyond a single manual upload.
Folder uploads and batch automation are exactly the extras the top rung asks for.
Beyond plain upload and folder creation from Flow and Apex, it adds asynchronous folder creation, batch copies of Salesforce Files and choices for duplicate names.
Last read on 2026-09-24Sources – 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Preview Kano · Delighter
Viewing a file inside Salesforce without downloading it.
Quick Preview opens a file in a pop-up window inside Salesforce for the file types Salesforce can preview, and a vendor demo shows a JPEG opening in a Preview window with Close and Download buttons. The separate Preview action opens the file in SharePoint's preview mode in a new browser tab, and the Winter '25 release added SharePoint preview for .msg and .eml files. Anonymous and portal users get Quick Preview only. Thumbnails, inline previews on the record page and preloading are not documented.
Quick Preview shows files inside Salesforce for the types Salesforce can render, with SharePoint's own preview in a new tab for the rest, which is taken as Complete; no thumbnails, inline or preloaded previews are documented for Extended.
Previewing is a person looking at a file, which a flow or code has no part in.
One rung higher: inline preview inside Salesforce is the default, with thumbnails and an allowDownload control on the preview API.
An inline viewer inside Salesforce clears Complete; thumbnails and the download control are what push it to Extended.
Looking at a file is a person's job, not something to automate.
Last read on 2026-09-24Sources – 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Original Access Kano · Dial
Getting from a Salesforce record to the source file in storage.
From the component, the Preview and Edit menu actions open a file in a new browser tab in SharePoint's preview or edit mode, file names can be clicked to open the file in SharePoint (since Summer '23), and an Open SharePoint button beside Upload Files goes to the record's folder in SharePoint. There is no choice of editor, and anonymous portal users and Android users cannot use these redirects.
Files open in SharePoint's own edit mode and the record folder opens in one click, which is Complete; there is no choice of desktop or web editor for Extended.
Opening the original in its storage is a click from the interface, with no automated equivalent.
Tied at Complete: a one-click Open in External Storage action covers files and folders, and a separate Open in Folder jump reaches storage directly.
Files and folders both open in storage in one click, which is Complete.
Jumping to the source file is an interface action with nothing to automate.
Last read on 2026-09-08Source – 1
Download Kano · Dealbreaker
Retrieving files from storage without leaving Salesforce.
Download is in the file menu for authenticated users and available to anonymous users, and the Quick Preview window has a Download button. No file-type or size limit is stated for downloads. Copy Public Link creates a link that anyone, or only people in the organisation, can use to view or download a file, with link type, expiry and password settings. Bulk, multi-select and folder downloads are not documented.
Single-file download from inside Salesforce with no stated type or size limit meets Complete; no bulk, multi-select or folder download is documented for Extended.
Download is scored as a user getting a file back out of storage, so it isn't rated for automation.
One rung higher: a multi-select bulk action downloads several files or whole folders at once.
Single-file download with no limits is Complete; downloading whole folders or many files at once earns Extended.
Scored as a person retrieving a file, so automation isn't rated.
Last read on 2026-09-08Source – 1
Rename Kano · Delighter
Renaming files and folders from Salesforce.
Rename is in the file and folder menus of the component for authenticated users; for anonymous users an admin must switch on file renaming, and folder renaming is available unless switched off. Renaming a Salesforce record does not rename its SharePoint folder: 24Files treats the new name as a new record and creates a new folder structure unless an admin sets up the Rename Record Folder Apex action, which ships with an example Flow. Errors are logged to the 24Files Error Logger object with coded messages, and the docs list characters that SharePoint does not accept in names. Bulk and inline renaming are not documented.
Files and folders can be renamed from inside Salesforce, with errors logged to an error object, which meets Complete; no bulk or inline renaming is documented for Extended.
The Rename Record Folder action renames record folders from Flow or Apex, and Upload Metadata renames files by writing the FileLeafRef field, so files and folders are covered from both, with nothing beyond the basics.
Tied at Complete: rename is a native action for both files and folders, and a List Action can add bulk rename.
Files and folders both rename natively, which is Complete.
Flow, Apex and the REST API all rename files and folders.
Delete Kano · Delighter
Deleting stored files and folders from inside Salesforce.
Delete is in the file and folder menus for authenticated users; for anonymous and portal users an admin must switch on file deletion, and folder deletion is available unless switched off. It removes one item at a time from the menus and acts on the item in SharePoint; the docs do not say whether deleted items go to the SharePoint recycle bin. Errors are logged to the 24Files Error Logger object. Bulk and multi-select deletion are not documented in the component.
Files and folders can be deleted from inside Salesforce, with errors logged, which meets Complete; there is no bulk or multi-select deletion in the component for Extended.
Remove Files and Remove Folders run from Flow (as Apex actions) and from Apex and accept lists of requests, so single and bulk deletes of files and folders are covered, with a response per request but nothing beyond the basics.
Tied at Complete: files and folders can both be deleted from the record widget, and a List Action can add bulk delete.
Files and folders can both be deleted, which is Complete.
Deletes run from Flow and Apex, including whole SharePoint drives and many items in a single Apex call.
Move / Copy Kano · Delighter
Relocating or duplicating files and folders without leaving Salesforce.
Move is in the file and folder menus of the component; for anonymous users an admin must switch on file moves, and folder moves are available unless switched off. The Move Folder or File Apex action, which also runs from Flow, moves a file or a folder with its subfolders and files between paths within the same SharePoint site and document library; after a record folder is moved, the folder-structure link must be reset so the component finds it again, as the vendor's example Flow and video show. No copy action for files or folders is documented, and no move between sites, libraries or storages.
Files and folders can be moved but not copied, which is the Limited anchor's 'only some combinations'; Complete needs every move and copy combination.
Moves run from both Flow and Apex through Move Folder or File, but only within one site and library, with a separate junction reset after record-folder moves, and there is no copy operation, so the capability is thin.
One rung higher: move works on single items and in bulk, with a destination picker and conflict handling, and copy runs through Flow.
Single and bulk moves, with a choice of destination and conflict handling, meet Complete.
Move and copy run in Flow and Apex on files and folders, and Apex can also move items between drives, which goes beyond a plain move.
Where this leaves Basic Ops: Both open the original, rename and delete at Complete. CloudFiles goes further on ingestion, preview, download and move and copy, with whole-folder uploads, bulk and folder downloads, and copy as well as move, where 24Files moves files but has no copy.
| Feature | Kano | 24Files rung | CloudFiles rung |
|---|---|---|---|
| Ingestion | Dealbreaker | L4 · Complete | L5 · Extended |
| Preview | Delighter | L4 · Complete | L5 · Extended |
| Original Access | Dial | L4 · Complete | L4 · Complete |
| Download | Dealbreaker | L4 · Complete | L5 · Extended |
| Rename | Delighter | L4 · Complete | L4 · Complete |
| Delete | Delighter | L4 · Complete | L4 · Complete |
| Move / Copy | Delighter | L3 · Limited | L4 · Complete |
Advanced Ops
Capabilities past basic file handling that separate a connector from a document system: editing files, version history, per-user permissions, metadata, and keeping Salesforce and storage in sync.
File Edit Kano · Delighter
Changing a document from Salesforce, and whose editor does the work.
Edit in the file menu opens the file in SharePoint's edit mode in a separate browser tab. In the Google Drive preview, Edit opens a spreadsheet as a Google Sheet in a new tab. No source shows editing inside the Salesforce window, and anonymous users cannot open files in edit mode. Copy Public Link can also create an edit link for people outside Salesforce.
The Edit button hands the file to the storage's own editor in a new tab, which is the Limited anchor; Complete needs editing inside the Salesforce window.
Editing a document's contents is done by a person in an editor, not by a flow or code.
Tied at Limited: the Edit button opens the file in the storage's own editor in one click.
One-click editing in the storage's own editor.
Changing a document's contents happens in an editor, by a person.
Versioning Kano · Distractor
Seeing and acting on a file's version history from Salesforce.
The 24Files docs, demo menus, listing and feature lists include no version history view, restore action or version log. The docs point to SharePoint's own version history: when an upload replaces a file with the same name (the default Replace setting), the previous version remains in SharePoint's version history. Users reach it by opening the file or folder in SharePoint through Preview, Edit or Open SharePoint.
Version history is reachable only by opening the file in SharePoint, which is the Workaround anchor; there is no version button of any kind for Limited.
Rated on viewing version history in the interface, which isn't an operation to automate.
Tied at Workaround: version history is kept in the storage, which is where it opens.
Version history lives in the storage, managed by the storage's own tools.
The feature is viewing history on screen, so automation doesn't come into it.
Permissions Kano · Dealbreaker
Whether each user sees only what their storage access allows, and how much Salesforce can control.
In authenticated mode each user signs in to SharePoint through the component with their own Microsoft account (OAuth with delegated permissions), so users see and act on only the files and folders SharePoint lets them reach, and each action is recorded against that user. 24Files does not set SharePoint permissions itself: Salesforce record access decides who sees the component, and admins can switch individual file and folder actions on or off per component. Copy Public Link lets users share a file by link with view or edit rights, for anyone or only the organisation, with an expiry date and password. Anonymous mode instead uses one shared service account, and nothing keeps Salesforce and SharePoint permissions in sync.
Per-user SharePoint permissions apply to every file and folder, with sharing links and action controls set by hand from Salesforce, which meets Complete; nothing syncs Salesforce and SharePoint permissions automatically, so not Extended.
No Flow or Apex action grants or revokes SharePoint permissions; the nearest route, Get File Link(s), returns an expiring public link from Flow or Apex, which gives access by link rather than by user and cannot be withdrawn by automation.
Tied at Complete: more than ten assignable Salesforce custom permissions sit on top of each user's own storage permissions, and Flow and Apex grant or revoke access at site, drive, folder or file level.
Granular permission control from the Salesforce side, which is Complete.
Owner, read or write access can be granted or revoked in Flow and Apex across nine storages, at site, drive, folder or file level, for users or groups.
Metadata Kano · Delighter
Reading and writing file properties and columns from Salesforce.
Admins choose which SharePoint columns the component shows and in what order, and which columns users must fill in at upload, with SharePoint's mandatory and multi-select settings applied. Since the Summer '26 release users can also edit metadata on existing files when an admin enables it. A field-mapping screen writes Salesforce field values to SharePoint columns at upload, including automatic uploads from Salesforce storage, and the Metadata Sync Apex action re-applies the mapping later, for example when a record changes. The docs state that managed metadata, person or group, hyperlink and lookup columns cannot be written through the Graph API, and mapped values are not updated after upload unless the sync action runs.
Admin-chosen columns are readable in the component and editable at and after upload, within the Graph API's limits, which meets Complete; mapping and set-on-upload exist, but 24Files does not go past the storage's limits (the unsupported column types stay unsupported), so Extended is not met.
Upload Metadata and Metadata Sync write columns from Flow (as Apex actions) and from Apex, and mappings also apply to automatic uploads, but managed metadata, person, hyperlink and lookup columns cannot be written and no action reads custom columns.
One rung higher: a View Metadata dialog and Get and Set Resource Property actions read and write metadata, including six SharePoint column types, and a documented workaround covers column types the storage API can't set.
Reading and writing metadata is the Complete bar; a documented route around the storage API's limits is what lifts it to Extended.
Flow and Apex read, write and search metadata, setting six SharePoint column types (single and multiple lines of text, number, yes/no, date and time, and choice), with a batch action for many files at once.
2-way sync Kano · Delighter
Keeping Salesforce and storage in step in both directions.
24Files keeps no copies of files: when a record page loads, the component reads the record's SharePoint folder through the SharePoint (Graph) API, so files and folders added, changed or removed in SharePoint appear on the next page load with no separate sync button, and uploads and changes made in Salesforce go straight to SharePoint. Vendor demos show a file uploaded in SharePoint appearing in the component and, in the Google Drive preview, a file added in Drive appearing after a page refresh. Files added natively to Salesforce Files, Notes & Attachments or Email-to-Case can be moved to SharePoint automatically. Reset Tracking is a manual menu option that resets the link between a record and its folder structure, not a sync control, and errors are logged to the 24Files Error Logger object.
Changes on either side appear in Salesforce on a page refresh with no separate sync step, which counts as instant sync under the rule used for this comparison and meets Extended; there is no dedicated sync control or sync log.
Sync already runs without anyone starting it, so there is no separate automation layer to rate.
Tied at Extended: three of CloudFiles' own pages describe instant two-way sync for files and folders.
Sync in both directions for files and folders is Complete; happening instantly is what makes it Extended.
Sync runs on its own already, leaving no separate automation to rate.
Where this leaves Advanced Ops: The two are level on 2-way sync at Extended, permissions at Complete, editing and version history. CloudFiles leads on metadata, with a documented workaround for SharePoint column types the storage API can't set, where 24Files cannot write managed metadata, person, hyperlink or lookup columns.
| Feature | Kano | 24Files rung | CloudFiles rung |
|---|---|---|---|
| File Edit | Delighter | L3 · Limited | L3 · Limited |
| Versioning | Distractor | L2 · Workaround | L2 · Workaround |
| Permissions | Dealbreaker | L4 · Complete | L4 · Complete |
| Metadata | Delighter | L4 · Complete | L5 · Extended |
| 2-way sync | Delighter | L5 · Extended | L5 · Extended |
Salesforce Support
How each product holds up across Salesforce surfaces beyond the Lightning desktop: external users in Experience Cloud portals, orgs still running Classic, and the Salesforce mobile app.
Experience Cloud Support Kano · Delighter
Letting external portal users work with files, and on what licence terms.
24Files can be placed on Experience Cloud record pages. In anonymous mode, portal users upload, download and quick-preview files in the record's Public folder through one shared service account, without a SharePoint licence, admins can also let them rename, move and delete files and add or edit metadata, and they can create, rename, move and delete folders unless an admin switches this off; portal users cannot leave the Public folder, open SharePoint or open files in SharePoint's preview or edit modes. Since version 4.300 a portal can instead run in authenticated mode, which needs a SharePoint account for each external user. Each portal user needs the 24Files Community User permission set and a 24Files licence unless the org has an org-wide licence.
Portal users work in Experience Cloud, but only inside one Public folder per record, through a shared account and with preview limited to Quick Preview, and the alternative authenticated mode needs a SharePoint account per user; this is limited access, which is Limited.
Flow and Apex actions can upload files to or remove them from the Public folder in anonymous mode and move files in or out of it by path, but no action shares or withdraws a file for portal users as such, so portal access is managed only by folder placement.
Last read on 2026-09-29Sources – 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Two rungs higher: portal users can edit and replace files as well as upload, download and preview them, with no storage licence needed, and admins control seven actions per user.
Upload, download and preview would be Complete; editing by portal users, per-user action controls and view tracking each go beyond it.
Share, unshare and list actions for portal users exist in both Flow and Apex.
Classic Support Kano · Distractor
Support for orgs still running Salesforce Classic.
The 24Files docs state that the product is available only for Salesforce Lightning because it is built as a Lightning component, and the prerequisites page tells admins to deploy Lightning, not Classic. The component is a Lightning Web Component, the older Aura version is deprecated, and the AppExchange listing declares Lightning readiness only.
The vendor states the product is Lightning only, so nothing appears in Classic and only Absent is met.
This is about which Salesforce interface the product renders in, not an operation that can be automated.
Three rungs higher: a first-party help article documents a Visualforce wrapper that renders the same widget in Classic as in Lightning.
The documentation says Classic gets the same widget as Lightning, with documented setup, which is Complete.
A question of which interface renders, not of automation.
Mobile Compatibility Kano · Distractor
How each product behaves in the Salesforce mobile app.
24Files runs in the Salesforce mobile app when an admin activates the record page for phone, and from version 7.91 (September 2026) it can be opened in the Field Service Mobile app as a Quick Action; the Field Service guide includes a phone screenshot of the component with Upload Files and the full file menu. The docs say it works on iPhones and iPads, but on Android users cannot sign in to SharePoint from the component and Preview, Edit and Open SharePoint do not work, leaving Quick Preview for supported types, which the vendor blames on a Salesforce Android app bug. The vendor site says files can be viewed and managed on any device and the listing declares mobile support, but the component is the same one used on desktop, and no phone-specific layout, camera capture or offline access is documented.
The component appears in the Salesforce mobile apps, but it is the desktop component placed on a phone page or opened as a Quick Action rather than a layout built for mobile, and Android loses sign-in, preview and SharePoint redirects, which fits Limited.
Whether the product renders in the mobile app is a question of interface, not of automation.
One rung higher: CloudFiles' help centre lists the file operations that work in the Salesforce mobile app and Field Service Mobile: browsing, previewing, uploading files and photos, downloading and opening files in storage.
The core file operations are documented for the Salesforce mobile app, which is Complete.
About rendering in the mobile app rather than running anything automatically.
Where this leaves Salesforce Support: CloudFiles leads on all three: portal users on Experience Cloud can edit and manage files under per-user controls, where 24Files limits them to one public folder per record through a shared account; and CloudFiles documents Classic support and a mobile layout, where 24Files is Lightning only.
| Feature | Kano | 24Files rung | CloudFiles rung |
|---|---|---|---|
| Experience Cloud Support | Delighter | L3 · Limited | L5 · Extended |
| Classic Support | Distractor | L1 · Absent | L4 · Complete |
| Mobile Compatibility | Distractor | L3 · Limited | L4 · Complete |
Data Reliability Score
The same three questions are asked of every item that feeds either score: is it public, who publishes it, and is it a checkable fact. Each component is averaged over the 31 items, and the Data Reliability Score is the average of the three.
| 24Files | CloudFiles | |
|---|---|---|
| Score · band | 85% · Well documented | 91% · Well documented |
| Coverage: is it public at all? | 100% | 97% |
| Independence: who publishes it? | 76% | 87% |
| Precision: is it a checkable fact? | 78% | 89% |
| What is public · what is not | Ten of the eighteen feature ratings also cite customer reviews or independent write-ups. The rest cite 24Files' own docs, website and demo videos; its Google Drive support appears only in an unlisted preview video. | All thirteen Enterprise Readiness items cite customer reviews, review sites or independent company profiles, and fourteen of the eighteen feature ratings cite customer reviews on AppExchange or independent consultancy write-ups, alongside CloudFiles' public security page, DPA and Trust Portal. |
Key data reliability issue: Capterra's only 24Files review is written by 24Flow's managing director, and one of its two G2 reviews matches a 24Flow co-founder, who also wrote the G2 profile overview. Neither is counted as independent.
Item by item: Coverage · Independence · Precision
Coverage: Found 1 · Partly 0.5 · Not public 0. Independence: third party, registry or marketplace data 1 · vendor copy on a platform, including sponsored reviews and branded articles, 0.5 · the vendor's own site or its maker's other products 0, taking the most independent source cited for the item. Precision: High 1 · Medium 0.5 · Low 0.25, and “n/a” where no precise figure is expected.
| Item | 24Files | CloudFiles |
|---|---|---|
| AppExchange reviewer company sizes | 1 · 1 · 1 | 0.5 · 1 · 0.5 |
| Named customers: modal profile | 1 · 1 · 0.5 | 1 · 1 · 1 |
| Pricing unit and tiers | 1 · 0.5 · 1 | 0.5 · 1 · 0.5 |
| Customer support | 1 · 1 · n/a | 1 · 1 · n/a |
| Conference and webinar presence | 1 · 1 · 0.5 | 1 · 1 · 1 |
| Hands-on evaluation | 1 · 0.5 · n/a | 1 · 1 · n/a |
| Security & Compliances | 1 · 0.5 · n/a | 1 · 1 · n/a |
| Help-doc architecture | 1 · 0.5 · 1 | 1 · 1 · 1 |
| API depth and gating | 1 · 0.5 · 1 | 1 · 1 · 1 |
| Stated ICP and messaging focus | 1 · 0.5 · 1 | 1 · 1 · 1 |
| Partner ecosystem | 1 · 1 · 0.5 | 1 · 1 · 1 |
| Team mix | 1 · 0.5 · 0.5 | 1 · 1 · 1 |
| Review-site profile richness | 1 · 1 · n/a | 1 · 1 · n/a |
| Storage Depth | 1 · 1 · n/a | 1 · 1 · n/a |
| Browse Library | 1 · 1 · n/a | 1 · 1 · n/a |
| Search | 1 · 0.5 · n/a | 1 · 1 · n/a |
| Ingestion | 1 · 1 · n/a | 1 · 1 · n/a |
| Preview | 1 · 1 · n/a | 1 · 1 · n/a |
| Original Access | 1 · 1 · n/a | 1 · 0 · n/a |
| Download | 1 · 0.5 · n/a | 1 · 0 · n/a |
| Rename | 1 · 0.5 · n/a | 1 · 1 · n/a |
| Delete | 1 · 0.5 · n/a | 1 · 0 · n/a |
| Move / Copy | 1 · 1 · n/a | 1 · 1 · n/a |
| File Edit | 1 · 1 · n/a | 1 · 1 · n/a |
| Versioning | 1 · 0.5 · n/a | 1 · 1 · n/a |
| Permissions | 1 · 0.5 · n/a | 1 · 1 · n/a |
| Metadata | 1 · 1 · n/a | 1 · 1 · n/a |
| 2-way sync | 1 · 1 · n/a | 1 · 1 · n/a |
| Experience Cloud Support | 1 · 1 · n/a | 1 · 1 · n/a |
| Classic Support | 1 · 0.5 · n/a | 1 · 0 · n/a |
| Mobile Compatibility | 1 · 0.5 · n/a | 1 · 1 · n/a |
The score reflects how much each vendor publishes, not how good the vendor is.
What changed
- 2026-09-29 · Baseline: this is the first cycle, so there is no earlier score to compare against.