The copy the signer keeps

When a request completes, everybody who signed something in it is sent their own copy, with the certificate recording how and when it was signed. Whether that arrives as a link back to the signing page or as a PDF attached to the message is set under Settings, Document output; a link is the default, because it keeps any identity check you asked for in front of the document. You do not have to send it to them.

What they get

Only the documents that person was asked to SIGN. Somebody asked to read a document is not a party to it and the certificate does not name them as one, so they are sent nothing.

The copy is the finished one: every signature stamped onto the page and the certificate bound in behind it. It is not the unsigned copy they were shown before they signed.

Attached, or a link

Under Settings, Finalisation, "How the signed copy reaches them" decides which. The choice is fixed onto each request when it is composed, so changing it never alters how a request already out will finish.

A link stays behind whatever identity check the signing was behind, because it is the same link they signed with rather than a new one. An attachment does not: somebody who had to pass a code to open the documents is emailed the finished ones as a file.

Where the documents are too large to travel in one message, the link is sent instead and the message says so.

Coming back to the link later

Their original link keeps working after the request is finished. It no longer opens the request (there is nothing left for them to do) and the page it shows now offers their signed copy to download.

A request that ended some other way, declined or withdrawn, has no signed copy at all, so that page says only that the request is closed.

If email has not been set up

Nothing is sent and the message log says so. The link above still works, and the signed copy is on the request for you to send on yourself.