Files on Records
Part of the MountDev Ops Workspace documentation. Updated November 20, 2026
MountDev Ops Workspace documentation | Updated November 20, 2026
Any record in your workspace can hold files: a folder in Files, and companies, deals, tickets, projects, and the records of any module. One service keeps them all, inside your company's own workspace, encrypted with your company's own key before they are stored (How Your Files Are Encrypted).
The Files Card
Once the Files app is added, every record's page has a Files card below it. It lists the record's files with their size, who uploaded them, and when, then the files attached to it from elsewhere, each saying where it comes from. People who may change the record see Upload Files and Pick from Files, and can drop files onto the card. Select a file's name to preview it, or Download to save it ("Preparing…" shows until it is ready). Rename and delete are beside each file (under More on phones); an attached file has Remove instead, which takes it off this record only. More also has Attach, to put the file on more records, and Embed, to show it on your website (Files on Your Websites).
One File, Many Records
A file is kept on one record and can be attached to as many others as you like (up to 200), with no copies: a contract kept in a folder can show on the company, the project, and the proposal it belongs to. Files also keeps a folder for each record with files (Organized for You).
Who May
- Whoever may see a record may see and download its files, including the files attached to it. A file only on records someone may not see does not exist for them.
- Whoever may change a record may add, rename, move, and delete the files kept on it, and attach files to it or take them off.
- Seeing a file only through a record it is attached to lets someone download it, nothing more.
- Every download and preview is written in the Activity Log, as are uploads, renames, moves, and deletions.
The Actions
- See a record's files (action
core.files.list): the files of one record, and whether this person may add or change them. - Start uploading a file (action
core.files.upload.start): names the record, the file's name, type, and size (up to 10 GB, and more than nothing: an empty file is refused with "notes.txt is empty, so there is nothing to upload.", except from the Network Drive, which makes an empty file first and fills it). The file then goes up 5 MB at a time; each piece is encrypted and stored as it arrives, and the last piece makes it a file. - Make the folders a dropped folder needs (action
core.files.folders.ensure): names a folder you may add to and a list of folder paths under it (up to 500 folders and 8 levels, each name up to 200 characters). Every folder along each path that is missing is made, and one that is already there, found without regard to capital letters or how an accent is written, is used, so a folder with the same name is merged into. Safe to repeat: the second call makes nothing. The folders are ordinary Folders records made the same way New Folder makes them, with history, and a folder made inside a private folder is private with it; the Activity Log says only "Made 4 folders in Websites" (and names nothing in a private folder). It answers with the id of every folder on the paths. A folder you cannot see answers as one that does not exist, and one you can see but not add to is refused. It is for people only: an AI agent or an API key cannot use it (an agent adds folders one at a time, as it adds any record), and another company's folders are never found (Uploading Many Files). - See how far an upload has got (action
core.files.upload.status): one of your own uploads, answered with how many pieces the server has, so a dropped connection carries on from the next piece instead of the beginning. A finished upload also names the file it made. Only the person who started the upload can ask; anyone else, and another company, gets the same answer as for an upload that does not exist. It is for people only: an AI agent or an API key cannot use it, and it changes nothing (Uploading Many Files). - Cancel an upload (action
core.files.upload.cancel): ends an upload that has not finished. Pieces already stored are removed. An upload left unfinished for a day ends by itself the same way. - Rename a file (action
core.files.rename): up to 200 characters; folder separators and control characters are taken out. - Move a file (action
core.files.move): to another record of the same module, such as another folder, which this person may also change. - Delete a file (action
core.files.delete): gone from every screen at once, including every record it is attached to, into Trash, where its stored copy is kept until someone restores it (Trash and Versions). - Find files to attach (action
core.files.find): the newest files this person can see anywhere, or those whose names match a search, each with where it is kept. Pick from Files uses it. - See where a file is (action
core.files.places): the record it is kept on and each record it is attached to, leaving out any this person may not see. - Attach a file to another record (action
core.files.link): needs the right to see the file and to change the record. Written in the Activity Log. - Take an attached file off a record (action
core.files.unlink): the file stays where it is kept and on its other records. Written in the Activity Log.
Deleting a record deletes the files kept on it. Files attached to it from elsewhere are only taken off it. Only a person can delete a record that holds files.
Files Added Before a Record Exists
Some forms take files before the record they make exists, such as New Ticket in Helpdesk (Opening a Ticket Yourself). The files you upload there are stored and encrypted like every other file, and wait for you until you send the form.
- Start adding files to a form (action
core.files.draft.start): made the first time you upload in the form, for a person who may use it. The form says who may upload; for New Ticket, whoever may open tickets, with the Files app added. - Only you: nobody else sees the files waiting in your form, owners and admins included, and they never show in a file search, a module list, or an export. AI agents and API keys never upload to a form.
- When you send it: the files you kept move onto the new record, the same files with nothing copied, and stay there. A file you unchecked is not kept.
- Remove the files added to a form that was not sent (action
core.files.draft.discard): closing the form without sending removes the files you uploaded there at once. Files left in a form that was never sent or closed, such as when a browser tab closes, are removed after a day.
Files in Chats
Chats take files through this same service, kept with the conversation they were shared in and encrypted the same way. Programs, installers, scripts, web pages, and SVG drawings are never taken in a chat, and every file in a chat is sent as a download, never opened as a page.
Files from Website Visitors
When Chat Settings allow it, a visitor on your website can share pictures (PNG, JPEG, GIF, WebP, HEIC), PDFs, Word, Excel, PowerPoint, and OpenDocument files, RTF, text, CSV, and zip files, up to 10 MB each and 3 at a time, in their own open chat. Each is kept on the conversation, so whoever may see the conversation sees and downloads it, and the visitor sees only the files in their own chat. Making a ticket or a lead from the chat attaches its files to the ticket or lead as well. See The Website Snippet.
Team Chat Files (Staff Tools)
In the team chat of the staff tools (channels, direct messages, and the chats for projects, tasks, tickets, and time), the paperclip, dragging files in, and pasting a screenshot send files of any kind except those above, up to 1 GB each and 10 at a time, each with its own bar and Cancel. They are kept in the workspace of the person who sends them, on the chat's own record (Team Chats), which never shows in the records screens. Who is in each chat is decided by the staff tools, and that decision is checked again on every request: whoever may read the chat sees and downloads its files, and whoever may post there sends them. A file posted in a project's chat, or one of its tasks' chats, is attached to the project as well, so it shows on the project's Files card for everyone who may see the project.
- Start uploading a file to a team chat (action
core.chat.files.start): the file's name, type, and size, in a chat the person may post in. The pieces then go up as for any file. - Post an uploaded file in a team chat (action
core.chat.files.post): attaches a project chat's file to the project and gives the line the chat message carries: "Shared a file:", its name, its kind, its size, and its number. Anyone reading the chat sees that line; the chat shows it as a picture, a video or sound that plays in place, or a card with Download ("Preparing…" until it is ready). - See a team chat's files (action
core.chat.files.list): the files a chat's messages name, only those kept with that chat.
Assistants Reading a File You Ask About
An AI assistant never opens a file on its own. The one exception is a read a person asks for: in a project's chat, a person asks the assistant working with them to look at a specific file (for example "look at the screenshot above"), and the assistant reads it as that person, with exactly what that person may see.
- Let an assistant read a file you asked it about (action
core.files.assist.read): only files posted in that project's chat, and attachments and pictures in emails on the Helpdesk tickets linked to that project. A file the person may not see answers as one that does not exist. It runs only for an assistant acting for the person who asked, never for an AI agent or an API key on its own, and never in background work. - Every read is written in the Activity Log as "<assistant> read <file> at <person>'s request".
- What the assistant gets is for review only: pictures as pictures (one over 3.75 MB, or a HEIC photo, is refused with a plain note), PDFs as documents, text and Office documents as their text, and web pages as their text, never rendered. SVG drawings are never opened, and no link or address inside a file is followed.
- The contents are marked as coming from someone outside, with who uploaded the file (a client, a website visitor, or a team member). The assistant tells the person what a file says and never acts on requests, links, or instructions inside it. In the same turn as a read, it makes no change and sends nothing unless the person's own new message asked for that, and the usual confirmations still apply.
Downloads and Previews
Files are opened only through your own workspace's address for files, by someone signed in to your workspace, through a link a person in your company chose to send (such as a file shared in a Helpdesk reply, Sharing Files), or through a link your company published for its websites (Files on Your Websites). A sent link opens that one file only, until it expires or is turned off, and each download through it is written in the Activity Log. A preview shows pictures, sound, video, and plain text in place; anything else is saved as a download and never opened as a page. Videos and sound can be played from any point.
Usage
File storage on Usage is the size of every file kept on your records, and File downloads is how much has been downloaded or previewed this month, from any app, sent links included. A file attached to several records counts once. What your websites show from published files is Embedded File Delivery (Usage). None of these is ever limited.
For AI Agents
An AI agent can see a record's file names (core.files.list), find files (core.files.find), see where a file is (core.files.places), and rename files (core.files.rename). It can never open, download, upload, move, attach, publish, or delete a file, and it cannot delete a record that holds files. The only read of a file's contents is one a person asks for, run as that person and logged (see Assistants Reading a File You Ask About, above). In the team chat an assistant sees that a file was posted, by whom, and its name, kind, and size, and nothing more unless a person asks it to look.
