Product journeys
What the product covers, at a glance.
Each family is a stage of the document journey. Open one to see its capabilities and the status of each.
Everything a document needs, from upload to evidence.
Available works today within the limits stated in its own line; some features need account configuration · On request built and ready for the operator to enable when requested · In roadmap not built yet; no delivery date.
Prepare
Everything that happens before anyone is invited: the PDF as you have it, the fields each person completes, the templates you reuse, the files that arrive from your drive or from a spreadsheet. Nothing is sent until you send it.
Available
PDF upload
Upload a PDF; nobody receives anything until you send it. The file stays as a draft while you choose who signs and where the fields go. A PDF that runs automatic actions on its own is refused, with the reason.
Available
Office and image conversion
Upload a Word or Excel file: we turn it into a PDF and you sign that. Word, Excel, PowerPoint, OpenDocument and image files are converted on the way in. The copy you sign is a clean archive-ready PDF, and the original is kept as evidence.
Available
PDF/A conversion
Your PDF is saved in a format made to last for decades; the original stays as proof. On each upload, or always if the account sets it, the PDF is rewritten to the PDF/A archive standard. Forms, documents already signed and documents with active content enter as they are, and the evidence record says why.
Available
Bulk send from spreadsheets
Send the same contract to up to 50 people from a spreadsheet, and see who gets in before you send. Choose a spreadsheet file and review the list first: how many people, the first five, and each row that does not fit, with its number and the reason. Everyone goes in or no one does.
Available
API field prefilling
Your own system fills in the fields before anyone opens the document. Your system sets the fields and their values through the API, the whole flow in one call if you like; the signer sees them filled in, and a locked value shows a padlock and cannot be changed.
Available
Reusable templates
The same form works for every new document. Save a document as a template with named roles and fields that fill themselves from whoever is signing. Start the next one from it and only check the people.
Available
Field validation rules
The field rejects a mistyped bank account number before anyone signs. A field can require a pattern (digits only, a document number, an IBAN) and a minimum and maximum. It is checked when typed and when it arrives from a spreadsheet.
Available
Visual field placement
Tap the page and the field stays right there. Place signature fields and data fields directly on the document, per person: move them, resize them, and mark which ones must be filled in before signing.
Available
Google Drive import
Pick a file in Google Drive and it enters as a draft. Choose the file in Google’s own picker instead of downloading it and uploading it again; the product sees only the file you pick. Available when your installation has Google set up.
Available
Fields from document tags
Write a tag in the PDF and the field appears there. A tag like [[SIG_1]] written in the document marks where a field goes, so a document that comes out of another system arrives with its fields already placed.
Available
Visual flow builder
People, order, roles, groups and the places on the document, drawn and moved by hand; a flow can be saved as a template without a document.
On request
OneDrive and SharePoint import
Bring the document straight from your cloud drive. Pick a file in OneDrive or SharePoint instead of downloading it and uploading it again. Enabled on request: the operator loads Microsoft’s details for the installation.
Decide who does what
Who fills in, who approves, who signs and who only receives a copy; in which order; with what level of identity; with a code shared another way when the document is sensitive.
Available
Signing routes
In order, all at once, or a separate copy for each person. Pick the route that fits the conversation: one signer after another, everyone on the same document, or one file and one record per recipient.
Available
Signature quorum
Three signatures out of five are enough: the rest are released on their own. Say how many of the invited people have to sign. When that number is reached the document completes, and whoever has not signed is released.
Available
Mixed signing methods
One person signs with their own certificate, another by consent, in the same document. Choose how each person signs. If someone is asked for a certificate the account cannot offer, the document is not sent, and it tells you who and what is missing.
Available
Approval before signing
Your manager approves before anyone signs, and the approval stays on the record. An approver comes before every signer, and nobody can sign until they approve. How they identified themselves is recorded; the PDF itself does not change. If they decline, the document ends.
Available
Reviewer access
Whoever has to review sees the document, without signing. A reviewer gets the link as soon as the document goes out and can download it if the sender allows. They never sign and never hold up anyone else’s turn.
Available
Reviewer: read receipt and notes
A reviewer reads it and can leave a note for the sender. That they reached the last page is recorded.
Available
Completion copies
Whoever needs to know receives the signed copy at the end. The signed PDF and the completion report reach them once the document is done. They are not invited at the start and are not part of the route before that.
Available
Download and print permissions
Control who can download or print the document. Both are allowed by default, and each can be turned off for one person without touching the others. Reading it in the browser always stays possible.
Available
Assign or replace signers
Reserve a signer’s place now and name the person later. The place waits with its own name, fields and signature boxes. You name the person, or replace one who has not signed, from the console or through the API, before or after sending.
Available
Required identity level
Ask for a minimum identity level per person: if they cannot prove it, they do not sign. Set low, substantial or high for each recipient, or in a template. Someone who has not proven it is offered the verification, and if they cannot, signing is refused before anything is signed.
Available
Recipient access codes
A separate code, shared another way, before the document opens. You set a code for one person, who must type it before the document opens. It never travels in an email or a link, and five wrong tries lock that person and tell you.
Available
Group signing
Anyone in a group can sign for the whole group. Name a group instead of a person: the first member who signs covers all of them, or as many as you ask. Each signature is the person’s own, and the record says it was for the group.
On request
Digital identity wallets
People would prove who they are with their country’s digital identity wallet. Today you enter with “Connect your wallet” when your account has one connected; the European wallet ecosystem would be switched on for your account when you ask.
Sign
How each person signs: by consent with their identification recorded, with their own certificate held by a provider, or after proving who they are with the country’s digital identity.
Available
Sign your own document
Sign it yourself in a minute, without inviting anyone. A real one-person document: the signing link opens on its own, and the record notes that whoever asked for it is who signed.
Available
Remote certificate signing
Sign with your own certificate: your key never leaves your provider. The signer identifies and signs through a connected trust service provider, with a certificate that is theirs. The document says up front that the certificate is required.
Available
Consent signing
Sign by consent, with the signer’s identification kept as evidence. The platform seals the document on the signer’s behalf after they confirm, and keeps their identification on the record. It is the quickest way to sign.
Available
Decline with a reason
Whoever disagrees declines and says why. A rejection carries its reason and goes on the record. The document’s policy decides whether it ends the document or lets it continue.
Available
Report a wrong recipient
“This is not for me”: say who it belongs to instead. The person records why the document is not theirs and, if they know it, who it belongs to. That reaches whoever sent it and stays on the record. The document remains signable meanwhile.
Available
Browser document viewer
Read it right in the browser, without downloading anything. The viewer opens the file directly, on desktop or phone. There is no separate download step before signing.
Available
Automatic signing reminders
Automatic reminders, so nobody has to chase the signers. Whoever has not signed yet gets an email reminder with the same link as the invitation, on a cadence the account sets. Each reminder is kept on the evidence record. Off until the account turns it on.
In roadmap
Personal certificate in console
You would link your personal certificate and sign straight from the console: connect the certificate that is yours once, then sign your own documents with it without leaving the console.
In roadmap
Document-bound signing approval
You would sign with a provider-held certificate, approving exactly the document you are signing. When the provider protects the key with SAM or an HSM password, the approval would be tied to this document: if it changes before you come back, nothing would be signed and you would press Sign again. Built against a laboratory stand-in, not yet measured against a provider.
Prove
What makes the result hold up: a certified time on every signature when a timestamp authority is enabled, long-term preservation, a sealed completion report, and a validator for any signed PDF.
Available
Timestamp without signing
Prove that a file existed at this exact time, without asking anyone to sign. A trusted timestamp authority certifies the time, and the file is stored closed. It is its own action, separate from sending a document out to sign.
Available
Signature timestamps
Every signature carries a certified time. A certified time is added to every signature when a timestamp authority is enabled for the installation. The time of each signature is certified by a timestamp authority.
Available
Long-term signature preservation
Built so it can still be checked long after the certificates expire. When the document closes, it keeps the proof of every signature plus a closing timestamp over the finished file. The closing timestamp is renewed before it expires, as a new version with its own entry in the evidence record. It depends on a timestamp service being enabled and on the stamps being renewed while the plan, or your own installation, keeps the document.
Available
Sealed completion report
A sealed report in the language of the document: who, when and how. Issued once when the document completes, sealed by the platform, in English, Spanish or Portuguese. It travels with the signed PDF.
Available
Signed PDF validation
Drop in any signed PDF and see what it says about each signature. Works on documents signed by other products too. It checks whether each signature matches the certificate in the file and shows the timestamps, and it is clear about what it does not judge.
Available
Changes between signed revisions
If anyone touched the document between signatures, we see it and name it. A replaced object, or a field that was reset after it was filled, is reported by name instead of staying quiet.
Available
Validation without file retention
Check a document without us keeping the file. The uploaded file is read in memory and discarded: its name, its content and its fingerprint are not stored.
Follow and close
What the sender sees while it happens and when it ends: who has acted, what is pending, reminders, and the closing with the package delivered.
Available
Email and event notifications
We let you know, and we let your systems know. Whoever sent the document always gets an email when it completes. Your systems get a call as well for each event you subscribed to.
Available
Automatic delivery package
Your system receives the signed PDF and the report by itself. When a document completes, the signed document and the completion report arrive together in one signed call, so you can file them without a second request.
Available
Recipient progress tracking
See where a document is stuck and for how long. For each person: notified, opened, signed, and the time between each step. Open Signers on any document.
Available
Signing activity and completion times
How many signatures per week, and how fast documents close. The last twelve weeks, with the typical time to close a document: the median, not the average, so one stuck document does not distort it.
Available
Filtered document export
Export the list with the same filters you are looking at. One click turns the documents on screen into a spreadsheet, keeping the filters you chose.
Your organization
Users, roles and permissions, your brand on what your signers see, and the defaults and limits that apply to every document your team sends.
Available
Account hierarchies
Distributor, resellers, subsidiaries: each one on its own level. Build a tree of accounts, or keep a single flat one. Each level sees only what is its own, and the database enforces it row by row.
Available
Custom branding
The signer sees your brand, not ours. Brand it at four levels: product, installation, account and document. What a signer sees is the sender’s identity.
Available
Users, roles and permissions
Each person sees and does what is theirs to do. Roles with permissions that are declared and checked independently, not just described on a screen. Someone without the permission does not see the option. Giving access to other people and defining roles belongs to the plans for organizations: a plan for one person has no users and no roles.
Available
Plan limits and usage
What your plan includes, and how much you have used. See what the plan includes, section by section, and what the current period has used against what the plan allows. A parent company sees the same for each child account. An item with no cap shows as uncapped, not as zero.
Available
Document defaults and limits
Every new document starts with your rules and your ceiling. Set what a new document starts with, and the most it is allowed: a retention ceiling of your own, or requiring everyone to sign with their own certificate. A document that exceeds a limit is refused, with a clear reason.
In roadmap
Organization sealing certificate
You would be able to seal your documents with your organization’s own certificate, uploading and managing it from the console.
Connect
The API and the webhooks: your system creates documents, names signers, reads the evidence and is told when each document moves.
Available
REST API and access tokens
A documented API, with a credential for each integration. A REST API described by an OpenAPI file, with tokens limited to what each integration needs.
Available
Duplicate-safe API retries
Retry without creating duplicates. Send an Idempotency-Key on calls that cannot be undone, and a retry with the same key returns the first answer without doing it twice. Answers are kept for 24 hours.
Available
Signed webhooks and retries
Your systems learn about every event, with a signature and retries. Approved, signed, rejected, completed and the rest, each signed so you can trust it, with a delivery log. After eight failures in a row the endpoint pauses and the people who can resume it are told.
Available
Local document assembly agent
The document is assembled inside your own network. A small agent paired to your company puts the document together there: the file and the signed PDF stay with you, and only the proof travels to the cloud.
On request
Organization security event export
Your organization’s security events, sent to your own monitoring tool. Sign-ins, policy and role changes, API tokens and every step of a document, in real time, to Elastic or to any secure web address. Only your organization’s events, with people as pseudonyms and never a document.
In roadmap
Embedded signing
Signing inside your own application, without sending people elsewhere, is planned. The signing screen would be embedded in your application with a short-lived token, so the signer would never leave it.
In roadmap
Watched folder signing
Dropping a PDF in a folder to send it out to sign is planned. A watched folder would send what you drop into it, and return the sealed result to the same place.
In roadmap
Document management connectors
Connecting your document manager to keep everything in one place is planned. Connectors for SharePoint, Google Drive, OneDrive and Salesforce would send documents out to sign and file the signed result back.
On request
No-code automation
You would connect Signing Flows with your systems without writing code. A flow of steps would send a document to sign, file what was signed or warn your team. Today it is shown in a guided demo, on request.
Operate
What the installation reports about itself: the plan and usage of each account, the providers and countries it offers, the state of each capability, its status page.
Available
Identity provider assurance limits
Declare up to what identity level each way of signing in can prove. Whoever runs the installation sets a ceiling for each identity provider. What the provider says decides, never above that ceiling; with none set, the level is low, so nothing changes until you say so.
Available
Public plan catalogue
Publish your plans and what each one includes. A public page lists every plan the installation offers, section by section, with the price quoted on request. “Ask for a quote” writes to the sales contact you declare.
On request
Status and uptime history
A status page with 90 days of availability. Shows whether each component of the installation is working now, its uptime over 90 days, and the incidents you open and resolve. Machines can read it too.
On request
Outage and recovery alerts
We tell you before your customers do. Up to five addresses get an email when a component goes down and stays that way, and another when it recovers. People who can resume a paused webhook are told too, with nothing to set up.
On request
Installation security event export
The security events of every organization, in your own monitoring tool. Whoever runs the installation connects its security tool once, and gets the events of every organization and of the platform itself, with people shown as pseudonyms. Two ready dashboards open with one click.
In roadmap
Backup and restore rehearsal
You would recover the installation from a backup that has been restored for real, with the record of when it was last rehearsed. Not rehearsed in this environment yet; no date.