PlatformDocuments
A document that is not attached to anything is just a file somewhere.
continON has one document service beneath every application rather than a file feature in each of them. A document is filed in a tree, attached to the record it concerns, and reachable from any domain that has business with that record — which is why the contract is still there when the purchase order is opened in another part of the organization.
What this page is about The descent of one document: where it came from, what it belongs to, who may act on it, and what was recorded. Everything below is that line, in order.
Where it comes from, and what it belongs to.
It arrives
Somebody puts it there
A file is filed into a folder in the tree, inherits that folder’s category, and — where it belongs to one — is attached to the record it concerns.
A process produces it
A transition in a running process resolves a template, merges the data its query returns, and writes the result into the same store as a PDF. Generation is a step in the work, not an export afterwards.
Document generation
Both land in the same store. There is not a separate place for the ones continON produced.
It is attached
A document sits in a folder, and a folder sits in a tree with a category and, where the same kind of document recurs, a template that standardises it. Separately from where it is filed, a document can belong to a record — an order, an employment record, a case, a request — and that attachment is what makes it travel. The domain that opens the record finds the document, without anybody having sent it anywhere.
Access is decided
A grant is not one switch. It is nine named rights, each one given or withheld individually — which is how somebody can be allowed to read and download a folder while being unable to change, move or share it.
Read
Open it and look at it.
Insert
Put a new file into this folder.
Update
Replace or amend what is there.
Delete
Remove it.
Copy
Duplicate it elsewhere.
Move
Relocate it in the tree.
Compress
Bundle a folder into a single archive.
Download
Take a copy out of continON.
Permission
Grant any of the other eight to somebody else.
Any of those nine, issued to
- A seatThe position in a unit. Resolves to whoever currently holds it, so it survives turnover.
- An employeeOne named person, where the access genuinely belongs to them rather than to their job.
- A partnerAn outside party, kept in its own account category rather than given an internal seat.
- EveryoneEvery account in the organization — used deliberately, not as a default.
It is recorded
Actions against a document are written to an activity record — what was done, by whom, and when. That is an audit trail of access and handling. It is not a version history, and this page does not describe it as one.
What a document store is usually assumed to do, and this one does not.
Document management is the component buyers assume the most about, so the assumptions are answered here rather than left to a later conversation.
- A retention policy engine — continON does not expire or dispose of documents on a schedule you configure.
- Records-management or archiving certification of any kind.
- Electronic signature. A document can be produced and stored; signing it is not something continON does.
- Version control. The store keeps an activity record of what was done to a file; it is not a version history you can roll back through.
- Text extraction from scans, or any automatic reading of what a document contains.
- An immutability or tamper-evidence guarantee on stored files.
Why there is no screen on this page A capture of the document store exists. It shows a folder tree naming real outside organizations and one person’s private folder, so publishing it would put other people’s information on a marketing page and imply relationships continON cannot evidence here. It is withheld until the same screen can be captured on demo data. Nothing has been drawn to stand in for it.
Why a grant to a seat outlives its holder
Grant a folder to a seat, then move the person out of it.
On a sanitized tenant: file a document, attach it to a record, grant a subset of the nine rights to a position, and watch what happens to that access when somebody changes job.