> 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-dv-public-trust-certificates/phase-1-steps/step-5-additional-information-optional.md).
# Step 5 - Additional Information (Optional)
This screen contains optional fields that help with managing and administering the certificate. None of these are required to get the certificate issued - but several are very useful and are recommended. This step is the same for all four DV variants.
#### Fields on This Screen
#### Tags *(with β+ Add Tagβ Button)*
* *Tags are labels that help categorize and organize certificate orders for easier tracking and reporting.*
* Common examples include:
* Project Name (e.g., "ProdApp")
* Environment (e.g., "Production", "UAT", "Development")
* Server Name
* Department or Business Unit
* Cost Center
* Tags are used internally within CERTInext and are not included in the certificate itself.
* *Click **+ Add Tag** to create a new tag.*
* *Multiple tags can be added to a single order.*
* Using tags is highly recommended to simplify searching, filtering, and reporting.
#### Order Remarks
* *Allows you to add internal notes related to the certificate request.*
* Remarks are visible only within CERTInext and are not included in the certificate.
* Useful for recording:
* Business justification
* Change request numbers
* Ticket references
* Renewal notes
* Deployment instructions
* Example:
* "Replacing certificate for production web server."
* "Renewal of expiring VPN certificate."
* *Leave blank if no additional comments are required.*
#### Technical Point of Contact (Technical POC)
* Allows you to specify the individual responsible for the technical management of the certificate.
* Typically used to identify:
* Server administrators
* Infrastructure teams
* Network administrators
* Application owners
* The Technical POC may be different from the requestor who submits the order.
* *Enable this option if technical ownership needs to be formally recorded.*
* Particularly useful in enterprise environments with multiple teams and administrators.
* *Leave disabled if not required.*
#### KYC Documents *(Optional)*
* *Allows supporting identity or business verification documents to be uploaded.*
* Some certificate types or account configurations may require document verification.
* Typical examples include:
* Business registration documents
* Organization verification documents
* Government-issued identification
* For most standard DV SSL/TLS certificates, KYC documents are not required.
* *Upload documents only when specifically requested during the certificate validation process.*
#### Additional Email Recipients
* Allows additional stakeholders to receive certificate-related notifications.
* Useful when multiple people need visibility into the certificate lifecycle.
* Typical recipients include:
* IT Administrators
* Security Teams
* Application Owners
* Operations Teams
* Project Managers
* These recipients can receive notifications such as:
* Order confirmations
* Domain validation requests
* Certificate issuance alerts
* Renewal reminders
* Revocation notifications
* *Enable the option and enter the required email addresses.*
#### Auto-Renew Certificates Until Coverage *(Enabled by Default)*
* Automatically renews and reissues certificates throughout the selected subscription coverage period.
* Helps ensure certificates do not expire unexpectedly.
* *Recommended for most production environments.*
* *When enabled:*
* *CERTInext automatically initiates the renewal process before certificate expiry.*
* *Renewal notifications are sent according to configured policies.*
* When disabled:
* Renewals must be performed manually.
* There is a higher risk of certificate expiry if renewal is overlooked.
* It is recommended to leave this option enabled unless there is a specific operational requirement for manual renewals.
#### Set Renew Criteria: Before \_\_ Days of Expiry
* *Defines how many days before certificate expiration the automatic renewal process should begin.*
* The default value is 15 days before expiry.
* Organizations can increase this value to provide additional time for:
* Validation activities
* Approval workflows
* Deployment planning
* Change management processes
* Example:
* 15 Days: Renewal starts 15 days before expiration.
* 30 Days: Renewal starts 30 days before expiration.
* 60 Days: Renewal starts 60 days before expiration.
* For large enterprises, a longer renewal window is often recommended to accommodate internal processes and avoid service disruption.
**π‘ TIP**
Even though all fields on this screen are optional, it is good practice to: (1) add at least a Tag such as 'Production Web Server' or 'Wildcard - All Subdomains' to make the certificate easy to find later, and (2) leave Auto-renew turned ON to avoid your website showing a security warning due to an expired certificate.
**π InCommon Note**
The Auto-renew feature works the same way for InCommon certificates. Since InCommon DV certificates are issued for 30 days/ 90 days / 199 days at a time, auto-renewal will trigger 15 days (or your set number of days) before each expiry. Make sure your institutional InCommon agreement is still active at renewal time so the renewed certificate is also covered under the agreement.
Click Back to go back, or 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-dv-public-trust-certificates/phase-1-steps/step-5-additional-information-optional.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.