> 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/ev-certificate-request-approval.md).
# EV Certificate Request Approval
*The Certificate Approver (the person you nominated in Step 5, Section B) will receive a separate email asking them to approve the EV Certificate request. This is an additional security check required specifically for EV certificates.*
**Email the Certificate Approver will receive:**
• Subject: "ORDER #\[Order ID] – Approve SSL EV Certificate request"
• The email states that a Code Signing – EV order has been submitted by a Certificate Requester and needs approval from the Certificate Approver role.
• It contains a button labeled "Approve EV Certificate request." The Certificate Approver must click this.
**What the Certificate Approver sees and does:**
• Clicking the button opens the emSign Subscriber portal and shows a "Consent Required" page.
• The page displays: Order ID, date ordered, ordered by (organization name), Certificate Requester Name, and a section titled "Approve Code Signing EV request."
• A message reads: "Please approve (or reject) the Code Signing EV certificate request."
• Two buttons are displayed: "Approve" (orange) and "Reject" (white).
• The Certificate Approver must click "Approve."
• A confirmation popup appears: "Are you sure you want to approve the SSL EV certificate request?" - click "Yes."
• A green success message will confirm the approval.
**⚠ IMPORTANT NOTE**
• The Certificate Approver is a different role from the Contract Signer, though they can be the same person. However, both approvals are separate actions and must be completed independently.
• Do not click "Reject" unless the request is invalid or unauthorized.
• After this approval, Action 3 will show as "Completed" and Action 2 (Subscriber Agreement) may reorder in the tracker based on sequence.
• The Certificate Approver should verify they recognize the Certificate Requester Name listed before approving.
• If the Certificate Approver is unable to complete this action, contact your CERTInext administrator to reassign the role.
---
# 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/ev-certificate-request-approval.md?ask=&goal=
```
`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.