E-learning made simple
- Upload own materials
- Videos, PDFs, tests
- See who is where
Not just storage — every step is logged, linked and retrievable.
Every generated PDF page has a unique QR code. Document name, company, employee, ID, timestamp, page number — traceable even when printed.
Employee and employer each receive a unique one-time code (OTP) that only they can redeem. Every confirmation is logged — who, when, from where.
Events are linked in a connected chain. If someone tries to modify an earlier entry, the change leaves a visible trace.
After every confirmation the system automatically generates an archived receipt. Retrievable and verifiable at any time.
All events, statuses and data are exportable. Internal review, compliance check — all the data is in one place.
Logical folder structure with role-based access. Employee, HR admin, payroll — everyone sees only what they should.
From onboarding data collection to acceptance and archiving, the process stays in one system — with less printing and less manual administration.
Required personal and HR data is collected once, in one place. HR doesn't have to re-type the same details.
All incoming data is visible in one workflow, so review stays quick and transparent.
Required HR documents are generated from the approved data without copy-paste work.
Documents can be accepted online with OTP or signed with QES for official use — without paper loops.
Final documents and acceptance trail are stored in a retrievable digital employee file.
The process can run end-to-end without printing and scanning.
Most systems just file the document away. oneDox runs the whole process — and proves it happened.
New-hire data capture, document generation and process steps in one flow.
OTP acceptance or QES signing — same surface, same audit trail.
Timestamps, event chain, archived acceptance receipt — every step recorded.
Independent verification, EU DSS validation, report and export — provable later, too.
Document + process + evidence — in one place.
Real screenshots from the flow — from the signing code to the post-signature receipt.
The document's path from generation to archive — same trail, same evidence.
You don't just sign something. You can also prove later who accepted what, when and under which conditions.
DAP (employee: download → external signing → upload) or connector (employer: SMS transaction code + signing PIN) — same flow, same evidence.
provider-agnosticIndependent EU DSS round for every signature: qualification level (QESIG / QES / AdES), Trust Service Provider, certificate chain and revocation status — eIDAS-traceable.
EU DSS validationTimestamp, device data, IP, acceptance context — sealed in an integrity-protected package.
evidence chainYears later, via link or QR — anyone with access can verify it for themselves.
long-term verifiableDAP, eIDAS QES or internal OTP acceptance — same flow, same evidence. The signing level is set per signer: on the same document the employee can use OTP and the employer can use QES. Employee-authenticated documents are validated via mandatory EU DSS verification before they're accepted.
A PDF signed by your QES provider can be uploaded, traceably logged and accepted after validation.
SMS transaction code + signing PIN → the connector signs the PDF → mandatory EU DSS round → save. Employer-side signing only starts after the employee-side EU DSS validation succeeds.
A signature is only worth something if it can be proven later. That's what we do.
Every issued document carries its own verification code. Anyone who scans it sees: real, untouched, and we know who accepted it — no login required.
A nyomtatott vagy továbbküldött oldal is visszavezethető az eredeti rekordhoz, így a HR csapat később sem marad bizonyíték nélkül.
Not just the file — a specific page is identifiable, even printed, photographed or forwarded.
The public QR carries no PII: only type, SHA-256, issue date and status are visible. The full Passport (signers, lifecycle) requires authenticated access.
The QR points to the acceptance evidence, not just the file — you see who accepted, and when.
No need to log into oneDox to confirm a document's authenticity.
Paperless operation — with paper-grade verifiability.
The system's goal is not just to produce the document — but to make it retrievable later exactly what happened.
Who accepted the document?
The system clearly shows which party confirmed the acceptance.
When did acceptance happen?
The timestamp is logged and retrievable at any time.
Which email address received the code?
The code delivery target is visible — no need to search through emails.
Which document version was in effect?
Acceptance is tied to the specific version, not just the filename.
Was a receipt generated?
The acceptance receipt is retrievable and verifiable separately.
Has the document changed since then?
If a modification occurred later, it is visibly traceable in the audit trail.
What status is the process in?
At a glance: awaiting acceptance, closed, or requires further review.
During an internal or external review, all this data is available in one place, in a readable format.
The steps of the employee and the employer are logged separately — so it's always visible later who accepted which document version and when.
Both the employee and the employer can confirm acceptance with their own unique one-time code. The system automatically tracks where each party is in the process.
An archived PDF receipt is generated for each acceptance — retrievable and verifiable at any time.
The system logs the time, parties, status and the linked document version. No need to search through emails and filenames during a later review.
A connected event chain in the background protects the integrity of the log — it works on the IT layer; HR doesn't need to deal with it.
The detailed technical solution can be found in the 'Technical background' section.
A simple, clear process that links the document, the acceptance and the review.
In the background, events are linked in a hash chain — subsequent modifications leave a visible trace.
The system assigns a unique identifier to every document and embeds two QR codes — whether the PDF was generated, admin-uploaded or QES-signed. One identifies the content; the other reveals the full document lifecycle — retrievable at any time, from anywhere.
Each document receives a nanoid-based unique identifier at generation time. This ID stays linked to every step of the lifecycle — from creation to archiving.
Left QR: the Passport URL where the lifecycle is viewable. Right QR: content-hash-based verification. Both appear on every single page — retrievable even when printed.
The Passport URL is publicly accessible: it shows the document's status and basic details. The full lifecycle is available with authenticated access (owner / admin).
Summary, Lifecycle, Signatures, Artifact chain and QR & Verification — each layer in its own tab. Admins additionally see the raw DSS payload.
Each signature on its own card: signer from the certificate, Trust Service Provider (TSP), DSS INDICATION (TOTAL_PASSED), qualification level (QESIG / QES / AdES), revocation status and the full DSS report — one click away.
Audit-ready reports help you quickly see which documents are signed, awaiting acceptance, expired or need review.
Audit-ready reports help you quickly see which documents are signed, awaiting acceptance, expired or need review.
This layer is for IT and review teams — on the HR side, only the key message is visible.
Events are arranged in a hash chain, so if an earlier entry were modified, the discrepancy is immediately visible. In the background, HMAC-SHA256 protects the chain; APP_SECRET is the system's own key, not user data.
The receipt summarises the version of the accepted document, the parties involved, the timestamp and the status. It is archived as a retrievable PDF.
Native acceptance is designed for internal HR processes; QES enables eIDAS-compatible signatures that are also valid for external processes. The two solutions serve different purposes, which is why they appear as separate use cases on the page.
The QR code carries the document name, the company, the employee, the document ID, the generation timestamp and the page number. After a single scan, the original record is retrievable.
Supports both cloud (SaaS) and on-site (on-site) deployment. Detailed service models are presented on the oneSolution page.
View details →HR School is One Solution's strategic partner: offering practical HR support, training, and interim solutions to ensure that system implementation and operations succeed not just technologically, but professionally as well.
One Learning Zrt.
1021 Budapest, Budakeszi 51/D C.ép. II/5