Getting a signature should not mean printing a contract, scanning it and e-mailing the result back and forth. AuraDoc lets you send any PDF in your workspace for signature from the same place where you store, search and read it. The people who sign do not need an account, a digital certificate or any software of their own: an e-mail invitation and a short code are enough. This article explains how a signing request works, what evidence is kept along the way and how the finished document can be checked later by anyone who receives it.
Sending a document for signature
Open a document and choose to request signatures. Add each signer with a name and an e-mail address, and AuraDoc sends them an invitation with a link to the document. When a signer opens the link, a six-digit one-time code is sent to the same address. Typing that code confirms that the person signing controls the inbox the invitation went to, which is the identity check most everyday agreements need. The code expires quickly and works only once, so a forwarded link on its own is not enough to sign in someone else's name.
While the request is open you can follow its progress from the document page: who has been invited, who has opened the link and who has already signed. There is no need to chase people by guesswork. Requests can also be started from outside the interface. The public REST API has an endpoint that asks for a signature on a document, and a signed webhook can tell your own system the moment the last signer finishes.
What the audit trail records
Every step leaves an entry in the audit trail. AuraDoc records when the invitation was sent, when the code was requested and confirmed, and when the signature was applied, together with the IP address and the browser of the signer. Entries are written in order, so the sequence of events reads like a timeline. The trail is tied to the document rather than to a mailbox, so it stays with the file in your workspace and can be exported when a customer, an auditor or a court asks how a signature was collected.
When everyone has signed, AuraDoc seals the PDF with a PAdES signature and, when the timestamp service is reachable, a timestamp issued by a trusted timestamp authority. A SHA-256 hash of the audit trail is embedded with the seal, which links the record of events to the exact bytes of the signed file. If a single character of the document changes after sealing, the signature no longer validates. If you already hold your own certificate in a .p12 or .pfx file, the PDF toolbox can also apply that certificate directly, which some regulated processes require.
Checking a signed PDF later
A signature is only useful if it can be checked. Members of your workspace can upload a signed PDF to the verification tool and see whether the seal is intact, which certificate produced it and when the timestamp was issued. The file is checked and then discarded; it is not stored in any workspace. The article on verifying a signed PDF walks through what each result means and what to do when a check fails.
Electronic signatures sit next to the rest of your security and compliance controls. Roles decide who may send requests, the audit trail lives beside consents and other privacy records, and documents stay encrypted in transit and isolated inside your organization's storage. You can compare what each plan includes on the pricing page, and related articles are grouped under the e-signature tag.