> 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-public-trust-certificates/phase-1-steps/step-6-authorized-signatory-information.md).

# Step 6 - Authorized Signatory Information

This step is unique to EV certificates. EV certificates require two specifically authorized individuals from your organization: a Contract Signer (who signs the legal Subscriber Agreement) and a Certificate Approver (who authorizes certificate issuance). These can be the same person if they hold appropriate authority.

&#x20;

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

&#x20;

### Contract Signer Information

The Contract Signer is the individual with authority to enter into legal agreements on behalf of your organization (e.g., Director, VP, authorized officer). They will receive and must electronically sign the eMudhra emSign Subscriber Agreement.

&#x20;

**Same as Organization Representative (checkbox)**

*Copies the Organization Representative's details from Step 4 into this section. Check this box if the same person from Step 4 is also your Contract Signer. The fields will auto-fill.*

&#x20;

**Choose User \*(required)\***

'New' or 'Existing' contact. *Select 'New' to enter new details, or 'Existing' to pick from saved contacts.*

&#x20;

**Name \*(required)\***

Full legal name of the Contract Signer. *Enter their full name exactly as it appears on official documents.*

&#x20;

**Email ID \*(required)\***

*Work email of the Contract Signer. The Subscriber Agreement signing link will be sent here. Enter a valid organizational work email. The agreement link is sent to this address. The Subscriber Agreement is a legally binding document - ensure this email reaches the correct authorized person.*

&#x20;

**Telephone**

Contact phone number (optional). *Select country code and enter the full telephone number.*

### Certificate Approver Information

The Certificate Approver is the individual who gives final authorization for the EV certificate to be issued (e.g., CISO, IT Director, delegated manager). This is an EV-specific requirement under CA/Browser Forum guidelines.

&#x20;

**Same as Contract Signer (checkbox)**

*Copies the Contract Signer's details into the Certificate Approver section. Check this if the same person is both Contract Signer and Certificate Approver (common in smaller organizations).*

&#x20;

**Choose User \*(required)\***

*'New' or 'Existing' contact. Select 'New' to enter new details, or 'Existing' to pick from saved contacts.*

&#x20;

**Name \*(required)\***

*Full legal name of the Certificate Approver.* *Enter their full name.*

&#x20;

**Email ID \*(required)\***

*Work email of the Approver. The EV Certificate Request Approval link will be sent here. Enter a valid organizational work email. Ensure the Approver is available and watching their email.*

&#x20;

**Telephone**

Contact phone number (optional). *Select country code and enter the full number.*

&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><p><strong>⚠ IMPORTANT</strong></p><p></p><p>The Contract Signer must have legal authority to bind your organization to contractual agreements (e.g., Director, VP, authorized officer).</p><p>The Certificate Approver must have authority to authorize security certificate issuance (e.g., CISO, IT Director, or delegated manager).</p><p>Both roles can be fulfilled by the same person if they hold appropriate authority.</p><p>Do not use external consultants or vendors in these roles.</p></td></tr></tbody></table>

*After completing the authorized signatory details, click Next to proceed to Step 7.*


---

# 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-public-trust-certificates/phase-1-steps/step-6-authorized-signatory-information.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.
