> 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-7-additional-information-optional.md).

# Step 7 - Additional Information (Optional)

This step is the same for both EV products. All fields are optional but some, such as auto-renewal, are pre-configured with sensible defaults.

&#x20;

<figure><img src="/files/0zXnvCxPsWYHcmYpmSXl" alt=""><figcaption></figcaption></figure>

&#x20;

### Screen Fields

&#x20;

**Tags**

Custom labels you can attach to this order for internal tracking and reporting within CERTInext (e.g., 'Production', 'Project-Alpha', '2026-Q2'). *Click '+ Add Tag', type your tag text, and press Enter. Add multiple tags as needed.* Tags are for your internal use only and do not appear on the certificate.

&#x20;

**Order Remarks**

A free-text notes field for any special instructions or internal references related to this order. *Type any notes relevant to your team or to support if you need to raise a query.* This text is visible to the CA and CERTInext administrators.

&#x20;

**Technical Point of Contact Information**

Checkbox - expands to collect the name, email, and phone number of the technical person responsible for managing this certificate (e.g., the system administrator who will install it). *Tick and fill in only if the technical contact is different from the Organization Representative entered in Step 4. Useful for larger organizations.*

&#x20;

**KYC Documents**

Checkbox - expands to allow you to upload Know Your Customer (KYC) verification documents (e.g., company registration certificate, utility bill, government ID). *Tick and upload documents if the CA requests them or if you want to proactively provide them to speed up the EV verification process.*

&#x20;

**Additional email recipients**

Checkbox - expands to add extra email addresses that should receive certificate-related notifications. *Tick and add email addresses if others in your organization (e.g., a manager, security team) should also receive order status updates and the download notification.*

&#x20;

**Auto-renew certificates until coverage**

Checkbox (ticked by default) - instructs CERTInext to automatically initiate certificate renewal before expiry. *Leave ticked (recommended). Only untick if you want to manage renewals manually. Without auto-renewal, your certificate may expire without notice, causing browsers to show security warnings.*

&#x20;

**Set renew criteria - Before \[N] days of certificate expiry**

*Configures how many days before expiry the auto-renewal process begins. Default is 15 days. Click the dropdown to adjust the lead time (e.g., 30 days gives more time for any renewal complications). 15 days is the standard minimum recommended.*

&#x20;

*Review and adjust any optional settings, then click Next to proceed to the Order Summary.*


---

# 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-7-additional-information-optional.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.
