Runs on real HR records
The signing route follows the org chart in HRM, not a hand-kept list of email addresses. When someone changes department, the route follows — you do not edit every workflow.
Digital administration is the third group in Apus Office, and the one a general office suite does not have. Incoming and outgoing documents, signing routes, seal custody and records retention run on the same HR records, the same org chart and the same permissions as the rest of Apus Platform.
Built for: Office managers · Records staff · HR-admin · Legal · Leadership
Authoring, spreadsheets, chat and meetings are table stakes — almost any toolset does them. What an organisation actually gets stuck on sits one layer down: an incoming document needs a register number, a due date and a named handler; a decision has to travel the right signing order; a seal has to record who took it out and which copy it went on. That is the layer generic office suites leave empty, and the reason this group exists.
The signing route follows the org chart in HRM, not a hand-kept list of email addresses. When someone changes department, the route follows — you do not edit every workflow.
Who submitted, who approved, when, on which version — kept with the document itself, so when the question comes back two years later the evidence is already there instead of being reconstructed.
Staff do not memorise another address and another password. Signing sits next to the Chat, Task and Drive they already have open all day.
The incoming document is given a register number, a summary line, a due date and a document type. The scan travels with the record instead of sitting in one person's inbox.
Routed to the unit or person responsible, with a deadline and a reminder. The discussion around it happens on the record, not in a side chat.
A multi-level signing route by permission, digital signature through a certificate authority, then the seal usage recorded in the register.
The outgoing document is numbered, sent to its recipients and filed under the retention period that document class carries.
Register numbering, retention periods and signing levels are configured against each organisation's own rules and settled during implementation. The software helps enforce the rules; it does not replace them.
In the first two groups of Apus Office it is broadly comparable — documents, chat, meetings, calendar. The difference is this group: a numbered document register with due dates, signing routes that follow the org chart, seal custody and records retention. That is what international office suites leave out, because it is bound to how administration actually works here.
Yes. The signing route connects to domestic certificate providers; the specific list lives on the integrations page. Scope and configuration are settled during solution design.
They are different and they work together. This group owns the ADMINISTRATIVE life of a document — register, assign, sign, issue. The EDM module owns the enterprise document store: versions, classification, and linking a document to the business record that produced it.
Yes, and that is the boundary with PM/PPM: administrative work stays here, and when a piece of work needs schedule, resources and cost it is promoted into a project task in PM/PPM without being re-entered.
Not on Apus Platform — Apus Office is included in every edition, so there is nothing extra to buy. The separately sold edition for small and mid-sized companies lives in Apus Suite.
Bring one real decision and one real signing route — the demo rebuilds exactly those on sample data.