Employee On–boarding Agreement with a BoldSign Bulk Link

This sample demonstrates how to collect an eSignature from a newly hired employee using a BoldSign bulk link. A single reusable signing URL is generated from a pre–prepared on–boarding document and then embedded directly inside the employer’s on–boarding email. The employee reviews the agreement and signs it inside an embedded BoldSign signing experience — without ever leaving the employer’s portal — and the host application is notified the moment signing completes.

What is a Bulk Link?

A bulk link is a special BoldSign signing URL created from a template or document that can be shared with many signers in sequence. Unlike a normal signature request where BoldSign emails a unique set of recipients, the bulk link is a single self–service URL:

• It can be shared by email, chat, or embedded in any web page — no recipient list is required up front.
• Every signer who opens the link gets their own copy of the document and signs independently.
• It is ideal when you do not know the exact recipients in advance — for example a job offer that is extended to one candidate at a time.
• It is perfect for embedding inside your own portal or notification email because the signing page lives on the BoldSign domain.

Scope of this Sample

This demo showcases the following capabilities:

• Reusable signing URL — one bulk link is pre–created from an on–boarding agreement document and reused for each candidate.
• Embedded signing experience — the bulk link is rendered inside a full–screen <iframe> so the signer never navigates away from the employer portal.
• PostMessage completion handshake — the BoldSign signing page posts an onDocumentSigned action (with the completed document id) back to the parent window when the employee finishes signing, so the host application can redirect to a thank–you page.
• Brand–consistent email — the demo simulates an on–boarding email with a single call–to–action button that launches the embedded signing flow.
• Completion tracking & download — the resulting document ID is surfaced on the completion page so it can be looked up in the test email inbox, and a Download signed document button streams the completed PDF back to the user.

Where it is Useful — Use Cases

End–to–end Workflow

1. Prepare the document once. An HR administrator uploads the on–boarding agreement into BoldSign and creates a bulk link from it. The link is tied to a single document ID.
2. Send the on–boarding email. The candidate receives a branded email that includes a single CTA button — accept and sign the on–boarding document.
3. Launch the embedded signing page. Clicking the button navigates to the host application’s /signdocument page, which loads the BoldSign bulk link inside a full–screen <iframe>.
4. Employee reviews & signs. BoldSign renders the secure signing experience inside the iframe — the employee reviews the role, salary, policies, and rules, then applies their signature.
5. BoldSign notifies the host app. When signing completes, BoldSign posts an onDocumentSigned message (carrying the completed document id) to the parent window.
6. Redirect to the thank–you page. The host reads the document id from the message payload and redirects to /signcompleted?documentId=..., which surfaces the document id and links to the test email inbox for verification.
7. Download the signed copy. The user clicks Download signed document; the completion page’s DownloadDocument handler calls the BoldSign SDK to download the completed document and streams it back to the browser as a single PDF.

How the Workflow is Implemented

The sample is split across three Razor Pages, each with a focused role:

Step 1 The On–boarding Email — Index.cshtml

The landing page is styled as an HR email from a fictional company (Treva) to a candidate (Richard). The body contains a single form whose submit button POSTs to the SignDocument page handler, simulating the candidate clicking the link in the email.

<form method="post" asp-page-handler="SignDocument" asp-page="/OnBoardingAgreement/SignDocument">
    <button class="card-link" type="submit">accept and sign the on–boarding document</button>
</form>

Step 2 Embedded Signing — SignDocument.cshtml

This page renders the BoldSign bulk link inside a borderless, full–screen <iframe> so the signing experience is indistinguishable from the host portal. A window.message event listener waits for BoldSign to post an onDocumentSigned action back into the parent window, extracts the completed document id from the payload, and redirects to the completion page.

var documentId = "70d38add-523c-4c0a-a812-12c330dbdfdb";

window.addEventListener("message", function (event) {
    const payload = event && event.data ? event.data : {};

    switch (payload.action) {
        case "onDocumentSigned":
            const docId = payload.documentId || "@documentId";
            if (docId && docId !== "undefined") {
                window.location.href =
                    '/on-board-agreement/signcompleted/?documentId=' + encodeURIComponent(docId);
            }
            break;

        case "onDocumentSigningFailed":
            console.log("Signing failed");
            break;
    }
});

<iframe src="https://app.boldsign.com/document/sign-bulk-links/?documentId=@documentId">
</iframe>

Step 3 Completion Page — SignCompleted.cshtml

Once the onDocumentSigned message is received, the parent page redirects here. The page reads the documentId from the query string, confirms the signature, surfaces the document id so it can be located in the test email inbox for verification, and offers a Download signed document button. Clicking the button calls the page’s DownloadDocument handler, which uses the BoldSign SDK to download the signed copy and stream it back to the browser as a single, openable PDF.

Step 4 PostMessage Handshake — Response.cshtml

BoldSign internally loads the response page inside the iframe which re–posts the completion signal up to the parent window so the host application can react:

<script type="text/javascript">
    parent.postMessage("SignCompleted");
</script>

Reference Links

• BoldSign Developer Documentation
• GitHub Source — BoldSign C# Samples
• Back to the live demo