Get documents signed — no email thread, no printer.
Store, version, share and sign documents — each filed against the project it belongs to, with full history and approvals.
What makes it unique
The features that set Documents apart from a generic ERP.
Built for projects-based manufacturing — not retrofitted to it. These are the workflows big ERPs either skip or get wrong.
Master + Copy register — distribute once, control forever
Designate a document as a Master (your authoritative SOP, manual or template) and issue tracked Copies to sister companies, sites or departments. When the master is revised, every copy gets pinged automatically with the new revision’s number.
Adobe-grade PKCS#7 cryptographic signatures
Real digital certificate signatures embedded directly into the PDF — opens in Acrobat with the green tick, verifies offline, and our server re-verifies the cert chain on every download. Not a JPEG signature pasted on a PDF.
Multi-signer placement workflow
Drag-and-drop signature fields onto the PDF canvas, assign each field to a specific signer, and send. Signers can sign in any order, on any device. The document only finalises when the last signer signs.
Linked to the entity, not floating in a folder
Every document is tagged to a project, customer, supplier, employee, asset or opportunity at upload time. Open the entity, see all its docs. No “which folder did Sarah save it in?”.
Annotation layer + comments on the PDF itself
Highlight, draw, drop comments on a specific clause or drawing detail. Comments thread inline, replies notify the author, and the annotations are saved with the document — visible to the next reviewer.
Department-based access control
Engineering sees calc files; QA sees NDE reports; Sales sees what they need. Set the department-access map once on a category; every new upload inherits it. No more share-link spreadsheets.
Feature 01
One module, six lenses — find any doc in three clicks.
The Documents module surfaces the same underlying register through six different views, each tuned for a different way you might be hunting: Master register for authoritative source docs, Copy register for distributed copies, Project view for everything filed against a single project, Search for full-text across the whole tenant, Folder tree for the nested structure inside a project, Trash for recovery. Same data, six lenses.
- Master register — your authoritative SOPs, manuals, templates, statutory certificates
- Copy register — every distributed copy of a master, with revision-pinging back to source
- Project view — every doc filed against a project, grouped by folder
- Search — full-text across titles, tags, descriptions, metadata; type-ahead suggestions
- Folder tree — nested folders inside each project for the natural document grouping
- Trash — soft-deleted docs recoverable for the retention window
Feature 02
Signatures that are evidence, not decoration.
Most ERPs let you paste an image of a signature on a PDF. ARKcelerate uses real PKCS#7 cryptographic certificates — embedded into the PDF in the same way Adobe Acrobat does — so when a customer’s auditor opens the file in Acrobat three years later, it shows the green tick, the signer’s identity, and a chain of trust that was verified at signing time. We re-verify the cert chain server-side on download too. Nothing about “trust me, that’s their signature”.
- PKCS#7 digital certificate signatures embedded into the PDF
- Drag-and-drop signature field placement on the canvas — one field per signer
- Multi-signer batch — send to N signers; document finalises when the last signs
- Signatures upload-verified — Adobe-signed PDFs uploaded externally are re-verified
- Tamper-evident: any post-signature edit forces a new version
- Audit trail — signer, timestamp, IP, certificate fingerprint — saved with the doc
Feature 03
Versioning + supersedes — the chain back through every revision.
Every upload creates a new version of the document. Older versions are preserved untouched. When a document is replaced (a new GA Rev. C supersedes Rev. B which superseded Rev. A), the supersedes-chain links each one — so opening Rev. A from three years ago shows you what came before, what came after, and which is current. Document numbers (e.g. ARK-DOC-0042) and revision codes (Rev. A, B, C) are first-class fields, not free-text.
- Every upload preserved as a separate, immutable version
- Document number + revision code as structured fields, not free-text
- Supersedes-chain links the lineage; opens visually like a version history graph
- Obsolete-mark (with reason) when a doc is retired
- Restore an old version to current with one click — retains its history
Feature 04
Retention, expiry, review cycles — every doc on a clock.
Documents with regulatory life-cycles (calibration certs, ISO certificates, employment contracts, statutory licences) carry an expiry date. Cross the threshold and an auto-task lands on the owner’s board — not in someone’s inbox to be missed. Review cycles run formal sign-off rounds: send to N reviewers, collect comments, route back for revision, finalise. Retention policies live at the category level — per-document overrides need a manager’s approval and stamp the audit log.
- Per-document expiry with configurable notice windows (30 / 14 / 7 days)
- Auto-tasks on the owner’s board on expiry approach
- Manager escalation when owner doesn’t act in time
- Review cycles with multiple reviewers, comments, and approval gates
- Retention policy at category level + per-doc overrides (audit-logged)
- Recycle bin holds soft-deleted docs for the retention window before purge
The projects-based manufacturing angle
A doc isn’t a file. It’s a contractual artefact tied to something that matters.
Customer-approved drawings drive BOM revisions, QC inspections and handover. Heat-lot MTCs underwrite warranty claims years later. Calibration certificates determine whether your QA reports are even valid. ARKcelerate treats every document as a record tied to its source-of-truth entity (project, customer, asset, employee) — not a loose file in a shared drive that nobody can find when the auditor walks in.
Everything in the module
The full Documents feature list.
Grouped by functional area. Every feature below is included in every plan — no paywalled tiers, no “enterprise edition” unlocks.
| Area | Features |
|---|---|
| One register, every entity |
|
| Folders, master register, and copies |
|
| Versioning, revisions, supersedes |
|
| Signatures + signature requests |
|
| Annotations, comments, review cycles |
|
| Retention, expiry, recycle bin |
|
| Search + audit log |
|
| Checklists & template packs |
|
Try Documents alongside every other module.
One signup. Full feature access during your trial.