#Sharing Files8 diskutieren mit

@Gene Connelly

My recommendation is to start with the storage your company already pays for. Most Microsoft 365 business plans include OneDrive and SharePoint, and Google Workspace includes Google Drive. Both handle common formats, including large PDFs, CSVs and zip files, even when a file won't preview in the browser. If you have neither, look at a Dropbox or Box business plan. S3 and Azure need technical setup before anyone can share from them. 

Getting files from clients.

For data files that are too big for email, use a file request. In OneDrive and SharePoint, it's called "Request files". You send the client a link, they upload without an account, and the files land in your folder without the client seeing anything else in it. Your admin has to switch it on, and you get an email each time a client uploads. Dropbox and Box business plans have file requests too. Google Drive doesn't, so if you're on Google, plan for this part. 

Keeping it secure.

Use a separate request folder for each client, and close the request once you have the files. When you send files out, share with the client's email address rather than an open link. 

Keeping it easy for your reps. Ideally, each account has one folder, linked from the account in Salesforce. Setting that up by hand for every new account is where things slip, and AppExchange apps for SharePoint and Google Drive handle it. CloudFiles is one of them, and for your setup it would look like this.

• Each new account gets its own folder in your SharePoint or Google Drive, shown right on the record.
• Clients upload through a CloudFiles link that drops their files straight into that folder, which also covers Google Drive.
• The link can be limited to the client's email address and protected with a password, and each upload can start a flow.

It's on the AppExchange at 

https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000Gh9uFUAR

Disclosure: I work at CloudFiles.

Thanks Usman. We're already using that approach: NavigationMixin with standard__namedPage / pageName "filePreview", passing recordIds and selectedRecordId. In the Salesforce mobile app it opens the native file viewer, and the user still has to tap Share and then Save to get the file onto the phone. 

What I'm trying to confirm: is there any supported way, standard or custom, for an LWC button in the Salesforce mobile app to save the file straight to device storage without going through the native viewer? Or is the native viewer the only option the app supports? A doc reference either way would really help. 

This is indeed a problem, especially with Email-to-Case, where all the files are owned by the system user. And you definitely don't want to give your users 'modify all data'. 

So with normal configuration nothing you can do. The only way is to build custom components, that then can run in system mode and therefore elevate the user beyond their normal permissions. 

Because this is a widespread issue, I created