Platform & Configuration
Document Management
Every continON application files its documents into one shared store — not per-app folders, not email attachments. Files are organized in a folder tree, permissioned by position, employee, or partner with nine distinct rights per grant, and stay attached to the orders, employees, and requests they document.
Reach begins atThe document
The operating model
Documents scatter because every system keeps its own: HR holds contracts, purchasing holds acceptance paperwork, and everything else lives in inboxes and shared drives where access is whoever remembers the link. continON runs one document service under all of its applications, so an employment contract, a goods-acceptance record, and a generated purchase confirmation are filed, secured, and retrieved the same way.
Access is the distinctive part. A grant on a folder or file carries nine separate rights — read, insert, update, delete, copy, move, compress, download, and the right to grant permissions onward — and targets a position in the org chart, an individual employee, a partner, or everyone. Position grants resolve to whoever holds the seat today, so document access survives turnover without a cleanup project.
The store governs documents; it does not generate them. Templates that merge process data into finished PDFs belong to the Builders — their output is filed here, next to what people upload, under the same folders, grants, and per-file activity log. Storage itself sits inside the platform’s database layer, not on ad-hoc network shares.
The subject
The document
- Folder and classification
- Version
- Position-based access
- Used in process
Reachable only by the positions granted it
Capture
A file is uploaded — or generated from a template by a running process — and lands in the store.
File
It is placed in the folder tree, categorized, and, where it documents a record, attached to it.
Permission
Grants go to positions, employees, partners, or everyone — nine separate rights per grant.
Work
The file travels with its request through approvals; operators open it from the record wherever they work.
Deliver
Export to PDF, download, or compress a folder into a single archive for handover.
Audit
The per-file log records the actions taken against the document — by whom, and when.
Everything inside Documents
4 capabilities
- Repository & Folders
How are documents organized so people find them by structure, not by memory? - File Operations
What can be done with a file once it is in the store — and is it tracked? - Permissions & Sharing
Who can see, change, or share each folder and file — and how does that stay current? - Attachments & Records
How do documents stay attached to the requests and records they belong to?
Connected through one operating model
Documents does not stand alone.
Records cross module boundaries without being re-entered — these are the relationships continON actually maintains.
- Builders
Generated PDFs are filed into the same tree as uploaded files. - System Administration
Document categories resolve from the shared lookup taxonomy. - Human Capital Management
Employee files attach to the employment record they document. - My continON
People upload documents to their own requests from self-service.
See Documents on your own operations.
A guided walkthrough on a sanitized demo tenant — this module, the shared platform, and a connected workflow end to end.