How to read a Sign&Grow certificate
Every line of the certificate of completion at the end of a signed PDF: where the software takes it from, what it shows, and what it does not.
What this page is
A description of what the software records and prints, written from its code. It is not a statement about any one document, not a sworn statement, and not legal advice. Whether an electronic signature is accepted, and what it proves, depends on the country and on the kind of document: ask a lawyer where you are.
Three things to keep in mind throughout. A name is the one the sender typed, attached to whoever used that person's link, which can be the sender. Times are in UTC. An internet address is a connection, not a place: many people can share one, and it can be the sender's own. And the certificate is made once, the moment the last person finishes. What happens after that (the completed copy being emailed, its first download by each person, later visits, a dispute) is only in the envelope's live audit trail: on the sender's envelope page, in the sender's evidence pack, and in part through a lookup by envelope ID on Verify a document.
Envelope
Envelope ID
Comes from: A random reference given to the envelope when it was created. The same ID is printed at the foot of every page of the documents and of the certificate.
Shows: Which envelope in our records the pages belong to. Anyone can look it up on Verify a document to see whether it was completed, when, how many pages and signers it has, the fingerprint of the signed file, and whether someone disputes it.
Does not show: It is not a secret and not a seal: anyone can type an ID onto a page. Compare the file itself, or its pages, with what the lookup says.
Subject
Comes from: What the sender typed.
Shows: What the sender called the envelope.
Does not show: Anything about what the documents say.
Status
Comes from: The state of the envelope when the signed PDF was made. A certificate is only ever made for a completed envelope, so it says Completed.
Shows: That everyone asked to sign, approve or view had finished.
Does not show: Anything that happened later, such as a dispute. The lookup by envelope ID shows that.
Sender
Comes from: The name and email address of the login that sent it, as they were when the PDF was made. That address was confirmed by a link sent to it before the account could send anything.
Shows: Which login sent the envelope, and that its holder could read that mailbox when it was confirmed.
Does not show: That the name is the person's real name: it is what they typed when they signed up.
Sent
Comes from: The moment the sender sent the envelope, in UTC.
Shows: When the envelope went out.
Does not show: When each person's email left; see Sent under each recipient.
Completed
Comes from: The moment the last person finished, in UTC. The signed PDF and its fingerprint are made right after.
Shows: When everyone had finished.
Signing order
Comes from: What the sender chose: Sequential (one after another, in the order shown) or Everyone at once.
Shows: Whether people were asked in turn.
Documents
Name and number of pages
Comes from: The file name as uploaded (the sender can rename it) and the page count read from the file.
Shows: Which files make up the envelope.
SHA-256 of the original
Comes from: The fingerprint of each file as the sender uploaded it, before anything was stamped on it.
Shows: Whether a file you hold is that exact upload: its SHA-256 must be the same.
Does not show: The fingerprint of the signed PDF itself, which cannot be printed inside the file it describes. That one is in every completion email, and Verify a document checks a file against it.
Recipients
One block for each person on the envelope, in the signing order.
Name (and, for a group, the member who acted for it)
Comes from: What the sender typed, or the name as corrected later. A signer can fix the spelling of their own name, and the sender can correct a name; the audit trail says when and by whom.
Shows: Who the sender meant this place on the document for.
Does not show: Who actually used the link. Whoever held the link could act under this name, and the sender can open a link too.
Role
Comes from: What the sender chose: Signer, Approver, Receives a copy, Needs to view, or In-person signer (signed on the sender's device).
Shows: What this person was asked to do.
Status
Comes from: What this person did: Signed, Approved, Viewed or Copied.
Shows: That their part was finished.
Sent
Comes from: The moment this person's turn started and our email to them was written, in UTC.
Shows: When they were asked.
Does not show: That an email left or arrived. The audit trail says “Sent to recipient” only when the mail server took the email, and “Not emailed” when none went out, for example for someone who signed in person or whose link the sender passed on.
Viewed
Comes from: The first time this person's link opened the document, in UTC.
Shows: That the link was opened then.
Does not show: Who opened it, or later visits. Later visits are in the live audit trail, at most one line a day for each person.
Completed, First completed, Completed again
Comes from: The moment this person pressed Finish (also to approve or confirm). When someone finished, the sender then changed the document, and they finished again, both moments are printed.
Shows: When their part was done, and that they did it again after a change. The audit trail says what changed.
Identity check
Comes from: The check the sender asked for before the document opened, and whether it was passed. The words are, for example: Link sent by email only; Link sent by email and an access code chosen by the sender; Link shared by the sender only; Signed in person on a device of the sender; or a one-time code by email or text message, passed at a time, with the masked address or number it went to.
Shows: What had to be got past before the document opened.
Does not show: Who the person is. Nothing here looks at an identity document. An access code is chosen by the sender, who can read it. Today “Link sent by email” is also printed for someone the audit trail lists as “Not emailed”: in that case the trail is right, and the link reached them some other way.
E-record consent
Comes from: The moment this person ticked that they agree to use electronic records and signatures, in UTC. Their audit line names the version of the wording their screen showed.
Shows: That this step was taken from their link. The wording of each version is on the help page, under “What do I agree to before I sign?”.
IP address
Comes from: The internet address of the request that finished their part, or of the first time their link opened if they have not finished.
Shows: Which internet connection the request came through.
Does not show: A place or a person. Many people can share one connection, and it can be the sender's own.
Time zone, and the times in their own zone
Comes from: What the person's device reported. The date of signing on the pages is the calendar day in that zone.
Shows: Which day the date printed on the pages rests on.
Does not show: Where the person was. A device can be set to any zone.
Reassigned from
Comes from: The person who passed the document on to this one.
Shows: That someone else was asked first and handed it over.
Signature picture
Comes from: The picture this person adopted: their name typed in a handwriting style, drawn with a finger or mouse, or a picture they uploaded.
Shows: The mark that was put on the pages.
Does not show: How it was made: the certificate does not say whether it was typed, drawn or uploaded, and the audit trail does not either.
Sent to, or Acted for (a group)
Comes from: The members of a group the document was sent to, as it was sent.
Shows: Everyone who could have acted for the group, and who did.
Audit trail
The sentence under the heading
Comes from: Printed on every certificate. It says the history cannot be edited without breaking the chain.
Shows: Each line of the audit trail carries a SHA-256 fingerprint made from the line itself and the fingerprint of the line before it. Changing or removing a past line without recomputing every line after it breaks the chain, and the app then shows that the record was altered. The chain has no secret key and is kept in the same database as the lines. So whoever can write to that database, the people who run the server or someone who broke into it, could change a line and recompute the rest, and the app would still show the record as intact. What would show such a rewrite is the chain head printed on the certificate of the completed PDF that each person was emailed: the stored trail must still lead to that same value. The browser description stored with a line is not part of its fingerprint.
Does not show: That nobody could rewrite the record. It shows that the stored lines were not edited without recomputing them, and the chain head below lets a copy someone already holds expose a rewrite.
Each line
Comes from: One line for each thing that happened before the certificate was made: the time in UTC; what happened, with its details; who (the name and address the line is signed with, or System for what the software did by itself); the internet address; the first 16 characters of the line's fingerprint; and, for someone whose device reported a time zone, their own time.
Shows: The record of the envelope up to completion, in order.
Does not show: Anything after completion, and anything listed as not recorded on the security page: whether an email was opened in the mailbox, how long a page was looked at, more than one later visit a day, how a signature was made.
Chain head
Comes from: The full fingerprint of the last line when the certificate was made.
Shows: The value the stored audit trail must still lead to. A sender's evidence pack lists every line with its fingerprint, so the two can be compared line by line.
Characters this PDF could not print
Comes from: Characters typed somewhere on the envelope for which the PDF has no font, listed by their Unicode number.
Shows: What was typed where the pages show a mark instead.
Signed without paper
Comes from: An estimate of the paper, water and CO2e not used, worked out from the number of pages.
Shows: An environmental estimate.
Does not show: Anything about the signatures.
On the pages of the documents
Sign&Grow Envelope ID at the foot of every page
Comes from: The envelope ID above.
Shows: Which envelope the page belongs to, also on a printed copy.
Does not show: That the page was not swapped or changed: compare it with the signed file.
Signed via Sign&Grow, with eight characters, under a signature
Comes from: The last eight characters of the internal reference of the person on the envelope the signature belongs to.
Shows: That the signature was placed by the software.
Does not show: Who it belongs to, to a reader: the certificate does not print that reference, so only we can match it, from our records, while we hold them.
NOT COMPLETED BY EVERYONE, and VOIDED, DECLINED or EXPIRED across the page
Comes from: Printed on every copy of an envelope that was voided, declined or ran out of time, which opens with a page that says why.
Shows: That it is not a signed document, whatever signatures are on it. Such a copy has no certificate.
Checking a certificate
- The file: choose it on Verify a document. A match means it is byte for byte the file stored when everyone finished.
- A printed or scanned copy: look up its envelope ID on the same page and compare the pages, the number of pages and the fingerprint.
- The record after completion: the sender can download the evidence pack from the envelope page. Anyone named on the document can mark it as disputed: see I am named on a document I did not sign.