Skay-Net DCC
A document control centre: you define the document types and their fields, DCC fills your DOCX templates, numbers each document, walks it through approval and keeps every version as a separate file with an immutable audit trail.
- Define document types with your own fields — a builder, not a developer ticket
- DOCX templates filled from {{placeholders}}, numbered CODE-YYYY-0001
- Guarded lifecycle: draft, approval, published, renewal, expiry, archive
- Approval chains per document type, with revision requests that come back to the owner
- Real versioning: each version keeps its own rendered file and field snapshot
- Archive to Local, SharePoint, OneDrive, Google Drive or Yandex Disk
- Edit templates in the browser through ONLYOFFICE · interface in EN · RU · TR
Frequently asked
Does DCC sign documents digitally?+
Not yet — and we would rather say so. Today you get approval chains, an immutable audit trail and full version history, which is what most document-control audits ask for. Server-side PDF sealing (PAdES) is the next item on the roadmap.
Can it write into our existing document storage?+
Yes. Generated documents are archived to the provider you pick: local/network storage, SharePoint, OneDrive, Google Drive or Yandex Disk. The provider is selected in system settings and credentials are tested from there.
How are versions kept?+
Each version renders its own file — nothing is overwritten — alongside a snapshot of the field values, the change note and who made it. Renewing or correcting a document creates the next version and leaves the previous one intact.