File Operations
What can be done with a file once it is in the store — and is it tracked?
Files in the store are worked on in place: upload one or many, rename, move, copy, update, and delete — with the grant on each folder deciding who may do which. Folders compress into a single archive for handover, and documents export without leaving the store.
Referenced across3 other parts of continON
How it works
Every operation is a permissioned action, not a free-for-all. Uploading, renaming, moving, copying, updating, and deleting each answer to a distinct right on the grant that covers the file, so allowing a team to read a folder does not quietly allow it to reorganize one. Multi-file upload handles the batch cases — an audit’s worth of evidence in one action.
Getting documents out is as governed as putting them in. A set of files or a whole folder — children included — compresses into a single archive for download, and documents export to PDF, with tabular data available as CSV. Downloading and compressing are themselves rights on the grant.
Actions leave a trail. The store keeps a per-file log recording actions against the document with the user and time, readable from the file itself — so when a file was opened, changed, or moved is an answer, not an argument.
What is filed, and who reaches it
File Operations
Bulk upload
Upload many files in one action — batch evidence and paperwork land together.
Per-action rights
Rename, move, copy, delete, download, and compress are each separately grantable actions.
Archive a folder to one download
Compress selected files or an entire folder, children included, into a single archive.
PDF and CSV export
Documents render to PDF and tabular content exports to CSV from within the store.
Per-file activity log
Actions against a file are recorded with user and time, and readable per file.
What this touches
See file operations running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.