> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-code-signing-certificates/phase-2-steps-via-email-and-emsign/subscriber-agreement.md).

# Subscriber Agreement

*The Contract Signer (the person you nominated in Step 5, Section A) will receive a separate email asking them to read and sign the Subscriber Agreement. This is a legal document between your organization and emSign.*

<figure><img src="/files/WokDAYpqK3A3trCUZbyC" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/caeWK7NybyR03mpjt0NA" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/C2HSV8U8fc1QYF2hgynO" alt=""><figcaption></figcaption></figure>

&#x20;

**Email the Contract Signer will receive:**

•     Subject: "ORDER #\[Order ID] – Sign Subscriber Agreement for EV SSL Request"

•     The email explains that a Code Signing - EV order has been submitted and requires the Subscriber Agreement to be signed by the Contract Signer role.

•     It contains a button labeled "Agreement Link." The Contract Signer must click this.

&#x20;

**What the Contract Signer sees and does:**

•     Clicking the "Agreement Link" button opens the emSign Subscriber portal.

•     The page shows the full Order Details: Order ID, date, product, organization name, and identifier.

•     A PDF of the Subscriber Agreement is displayed on screen. The Contract Signer must read through this agreement (it is typically 10 pages).

•     On the right side of the screen is an "Accept Agreement" panel containing:

◦     Your Name - Pre-filled with the Contract Signer's name. Verify this is correct.

◦     Place - The city/location where the agreement is being signed. Enter the applicable city.

◦     Email ID - The Contract Signer's email address (partially masked for privacy).

◦     Checkbox: "I am the authorized person to sign this agreement" - Must be checked.

◦     Checkbox: "I agree to all the terms & conditions of this agreement" - Must be checked.

•     Click the orange "Accept Agreement" button to sign and submit.

•     After successful submission, a green success message will appear.

&#x20;

**⚠  IMPORTANT NOTE**

•  The Contract Signer must be the one completing this step, not the applicant. Do not attempt to complete this step on someone else's behalf unless you are explicitly authorized.

•  The Contract Signer must check both checkboxes before the "Accept Agreement" button becomes active.

•  The Subscriber Agreement is a binding legal document. Ensure the Contract Signer reads it before accepting.

•  After accepting, Action 2 (Subscriber Agreement) will show as "Completed" on the Order Actions tracker.

•  If the Contract Signer does not receive the email, ask them to check their spam/junk folder, or contact your CERTInext administrator to resend the agreement link.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-code-signing-certificates/phase-2-steps-via-email-and-emsign/subscriber-agreement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
