HyoNova Sign
HyoNova Sign (Beta) sends PDFs for electronic signature, collects signatures with or without a HyoNova account, and seals the evidence of every agreement.
On this page
Simple electronic signatures with an evidence trail; not a qualified (QES) or advanced electronic signature.
HyoNova Sign lets your company send a PDF for signature, collect electronic signatures from colleagues and from people outside the company, and keep a sealed record of everything that happened. When everyone has signed, HyoNova produces the signed PDF, a certificate of completion and an evidence record that anyone with the verification link can check.
Sign is part of your company workspace, not a separate product. It uses the same company, the same people, the same roles and the same files. Open it from Sign in the sidebar of the company workspace.
What is in Sign#
| Part | What it does | Guide |
|---|---|---|
| Signature requests | Send one or more PDFs to signers, approvers and people who receive a copy, in a set order, with a message, an expiry date and reminders | Send a document for signature |
| Field editor | Place signature, initials, date, name and other fields on the pages and assign each to a recipient | Send a document for signature |
| Templates | Save a prepared request and reuse its documents, roles and fields | Send a document for signature |
| Signing | Recipients sign from a secure email link without an account, or inside the workspace if they are members, in English or Arabic, on a phone or a computer | Sign a document |
| Completion evidence | A signed PDF, a certificate of completion, document fingerprints, a chained activity record and a seal over the evidence | Evidence and verification |
| Public verification | A page where anyone with the verification link can confirm the record and check a PDF against it | Evidence and verification |
| Settings and evidence | Company rules for signing, authentication, reminders and downloads, plus usage and the state of the evidence seal | Sign settings and evidence |
Where you find Sign#
- Sign in the sidebar opens the Sign area: Overview, Documents and Templates.
- New › Signature request in the workspace starts a request from anywhere.
- Home shows a card when documents are waiting for your signature.
- Files has a Send for signature action on PDF files, and signed documents carry a Signed label.
- Search finds agreements you can see.
- In an office world, a compact Sign panel lists what is waiting for you so you can review and sign there. Preparing a request opens Sign in the dashboard.
- Company administration › HyoNova Sign has Signature settings and Retention & evidence for administrators.
Start in minutes#
- Open Sign. In the sidebar, choose Sign, then New signature request.
- Add the document. Upload a PDF or choose one from HyoNova Files.
- Add recipients. Choose company members or add external people by name and email, give each a role and a signing order.
- Place the fields. Drop at least one signature field for every signer on the pages.
- Choose security and send. Pick the authentication, the expiry and reminders, check the summary and choose Send for signature.
- Follow progress. The request shows who has signed and who is next. When everyone has finished, the signed PDF and the certificate appear on the request and in Files.
Statuses#
| Status | Meaning |
|---|---|
| Draft | Being prepared. Nothing has been sent |
| Sent | Sent to the first recipients; nobody has acted yet |
| In progress | At least one recipient has acted and others still need to |
| Finalizing | Everyone has finished. HyoNova is producing the signed PDF, sealing the evidence and creating the certificate |
| Completed | Signed by everyone and sealed. The final documents and the certificate are ready |
| Declined | A recipient declined to sign. The request stops for everyone |
| Voided | The sender cancelled the request with a reason. Nobody can sign any more |
| Expired | The expiry date passed before everyone finished |
Once a request is sent, its documents, fields and signing order are frozen. To change the content, void it and send a new request.
Who can do what#
What people can do in Sign follows their company role. The server checks every action.
| Role | In Sign |
|---|---|
| Owner and Admin | Everything, including Sign administration: see all the company's agreements, change Signature settings and view Retention & evidence |
| Manager | Create and send requests, manage and download their own requests, and sign what they are asked to sign |
| Employee | See and sign the agreements they take part in |
Apart from Sign administrators, people see only the requests they take part in — as sender, recipient, or colleague the request was shared with. Agreements are classified Confidential.
Show technical details
Sign uses the sign.* permission keys: sign.read, sign.create, sign.update, sign.delete, sign.export and sign.admin. Owner and Admin hold all of them. Manager holds sign.read, sign.create, sign.update, sign.delete and sign.export. Employee holds sign.read. Only sign.admin sees agreements the person does not take part in. The company must also have the Sign module (module.sign); during early access it is switched on for workspaces.
Plan limits#
Your plan can set three limits for Sign:
| Limit | What it counts |
|---|---|
| Requests per month | Signature requests sent in a calendar month, counted once per request |
| Recipients per request | Recipients on one request |
| Templates | Active templates |
Where your plan sets no limit, Sign shows No limit. When a limit is reached, Sign says Your plan limit for HyoNova Sign was reached. Administrators can see the usage in Retention & evidence.
Emails Sign sends#
Recipients and senders receive emails for an invitation, a reminder, a completed request, a declined request, a voided request, an expired request and a one-time code. If HyoNova cannot deliver email, the request shows it — for example Could not be delivered or Email unavailable — and the sender can copy the signing link and share it themselves. HyoNova never shows an email as delivered when it was not.
Privacy and security#
- Recipients see only their request. A signing link opens only the documents of that request, for that recipient.
- Links and codes are protected. Signing links and one-time codes are never stored in readable form, and signing links expire.
- Sent documents cannot change. Each document's SHA-256 fingerprint is recorded when the request is sent and again when it is completed.
- The platform team does not read agreements. HyoNova's own staff see only aggregate figures and health for Sign in Control Center, never agreement content.
How Sign connects to the rest of HyoNova#
- Files. Send a PDF from Files for signature. The signed PDF and the certificate of completion are stored back in Files with a Signed label.
- Customers and work. Link a request to records such as customers, deals, projects or tasks so the agreement is easy to find from them. See Customers.
- Office world. Review and sign what is waiting for you without leaving the world.
- Email. Invitations, reminders and results go out through HyoNova's email delivery. See Email delivery.
- People and roles. Who can send, see and administer Sign follows your company's roles. See Roles and permissions.
Status and limits#
- Beta. Sign works in early-access workspaces; behaviour and limits may still change.
- PDF only. Up to 10 MB and 500 pages per document; password-protected, already digitally signed, scripted or interactive-form PDFs are refused.
- Simple electronic signatures. Not QES or advanced electronic signatures; no trusted timestamp yet.
- Something not working? See Troubleshooting.
| Feature | Status | Notes |
|---|---|---|
| HyoNova Sign requests | BetaWorks today in early-access workspaces. Behaviour and limits may still change. | Send PDFs for electronic signature to signers, approvers and copy recipients, in sequence or in parallel, with expiry, reminders and an optional email code. Simple electronic signatures with an evidence trail; not a qualified (QES) or advanced electronic signature. |
| Signature field editor | BetaWorks today in early-access workspaces. Behaviour and limits may still change. | Place signature, initials, date, name, text, checkbox and other fields on PDF pages, assign them to recipients, and position them with the mouse, keyboard or exact values. |
| Signature templates | BetaWorks today in early-access workspaces. Behaviour and limits may still change. | Save a prepared request as a template and reuse its documents, roles and fields for new requests. |
| Signing without an account | BetaWorks today in early-access workspaces. Behaviour and limits may still change. | Recipients sign from a secure email link or inside the workspace, with an optional email code, a consent disclosure, drawn, typed or uploaded signatures, and decline with a reason. |
| Sealed completion evidence | BetaWorks today in early-access workspaces. Behaviour and limits may still change. | A flattened signed PDF, a bilingual certificate of completion, document fingerprints, a hash-chained activity record and a sealed evidence package. No trusted third-party timestamp yet; it shows 'Not configured'. |
| Public verification | BetaWorks today in early-access workspaces. Behaviour and limits may still change. | Anyone with the verification link can confirm a completed record and check a PDF against it in the browser, without uploading it. |
| Sign settings and evidence | BetaWorks today in early-access workspaces. Behaviour and limits may still change. | Company rules for external signing, authentication, expiry, reminders and downloads, with the evidence seal state and plan usage. |
Was this page helpful?
Thanks. Page ratings are not collected yet, so nothing was sent. If something is missing or wrong, see the Get help page.