Documents
Contracts, certificates and protocols next to the record they belong to - with versions, discussion and external sharing.
A document in a separate system gets lost
Keeping documents on a separate platform is possible and looks more powerful at first. But in an ERP the value of a document is its link to a RECORD: this protocol belongs to this batch, this contract to this customer.
A separate system also means a second database, a second upgrade, a second backup and a second security patch. For a small team those are real risks.
So documents live inside the system: permissions are already tied to the record, which means someone who cannot see the batch cannot see its protocol either.
Area, version, sharing
Documents are grouped into areas - contracts, certificates, laboratory protocols. Every document keeps its versions: who replaced what, and when.
To share with an outside party a link is created with a time limit and a download cap - no system account has to be given to the other side.
What this module adds
In the system this module opens the following items.
Related modules
Core
The foundation every module stands on: targets, signals, the metric store and permission groups - with no industry baked in.
Branding
The interface in your brand: name, logo, colours, email footer and login screen.
Language and terminology
Three languages - Azerbaijani, English, Russian - and the customer's own terms written into the interface.
Most often asked
Does an expiring document warn you?
Yes - contract and certificate end dates are tracked and a signal is raised as the date approaches.
Can a shared link be withdrawn?
Yes, a link can be closed at any time; the number of downloads can be capped as well.
See this module with your own data
The demo database is full of real documents - not a mock-up. Send a request and we will walk through your scenario.