Who Can Load a File
Part of the MountDev Ops Files documentation. Updated November 20, 2026
MountDev Ops Files documentation | Updated November 20, 2026
Every file is Private or Public. A new file is Private unless you choose Public when you upload it. You can change it later.
- Private: the file loads only for signed in people of your company who may see it, or through a short lived address made for one of them (a preview or a download). It has no public address.
- Public: the file has a public address that works with no sign in. The address exists only while the file is Public.
A chip with the word Private or Public shows on every file.
At Upload
Choose Upload Files in a folder. The pop up lists where the files will land and asks Who Can Load This, with Private selected and Public as the other choice: "Anyone with the address can load it, with no sign-in." Several files share one choice, with Choose for each file to set them one by one. A file is stored Private first and made Public right after, so it is never public by accident. The choice is saved as you made it: after each file is stored, the upload tray asks for Public and reads the answer. A file that could not be made Public stays Private, and the tray lists it with the reason until you dismiss it (Uploading Many Files).
A folder can remember a choice for new files: New Files Are Private (or Public) on the folder's page. It is only where the upload pop up starts (action core.files.folder_choice.set). Files already in the folder keep their own choice.
Change It Later
Open a file's More, then Who Can Load This (or Used In, which has the same switch). Whoever may change the file can do it (action core.files.visibility.set). Both choices ask first and list the places that use the file:
- Make Public: "Anyone with the address can load this file. It will be public on N websites."
- Make Private: "The public address stops working for good. A copy may still show for up to 10 minutes for anyone who already loaded it. Pages that use it will show a missing picture until you choose again."
Turning a file Private ends its public address for good. Making it Public again makes a new address, and links made earlier stay dead. Public files are sent with a ten minute cache (Cache-Control: public, max-age=600); private files are never cached (private, no-store).
Public needs Files on Your Websites turned on in Files, Settings, because a public address is the same thing as publishing the file. Publishing a file for a website (Embed) is the same switch as Public: the Embed window and its Only on These Websites list stay, on a Public file.
Files That Can Never Be Public
These have no Public choice at upload, in More, or in the picker, and the refusal says why:
- Files kept for an app that is Never Public: Meetings, Contracts, Invoices, Proposals, Helpdesk, Calls, Channels, Chat, and Projects. A file on a record of an app with no public rule is also never public (App Folders).
- Files in a private folder.
- Files in Trash. Restore them first.
- Anything new on a closed account.
A file that is already in a never public place reads Private, whatever it was before.
Files from Before
Files that existed before this change keep working exactly as they did. A file you already published for a website reads Public. Every other file reads Private. Nothing about them was rewritten.
Publishing a Website with Private Pictures
A page can use a Private picture while it is a draft. Visitors on the published website cannot load a Private file, so Publish checks first. If a picture the pages use is Private, a pop up lists each picture and the pages that use it, with three choices:
- Make Public and Publish: makes only the listed pictures Public, then publishes. Not offered when a picture can never be public.
- Publish Without Them: publishes, and each page shows its text and the picture's description instead of a broken image. Nothing becomes Public.
- Cancel: nothing changes.
See Publishing.
