> 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-ov-public-trust-certificates/phase-1-steps/step-3-organization-information.md).

# Step 3 - Organization Information

This step links your certificate order to a legally verified organization. The CA will validate your organization's details before issuing the certificate.

&#x20;

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

&#x20;

**Instant Issuance - Pre-validated Organizations**&#x20;

*If your organization has been previously validated by the CA, you will see an 'Instant' badge next to it and a green notice: 'You have 1 validated organization(s) - Instant issuance available.'*

*Selecting a pre-validated organization skips the organization re-validation wait, significantly speeding up certificate issuance.*

New organizations require validation, which typically takes 1-3 business days.

&#x20;

#### Selecting Your Organization

*The screen shows a list of your account's organizations. Use the tabs to filter: All, Validated, or Pending. Click the row of your organization to select it. The fields below will auto-populate.*

&#x20;

**Organization selector**: A searchable list of organizations linked to your CERTInext account. Each entry shows the organization name, ID number, location, and validation status. *Click on your organization's row to select it. If you have only one organization, it will appear pre-selected*.

**+ Add a new organization**: Button to register an organization that is not yet in the system. *Click only if your organization does not appear in the list*. New organizations must complete a validation process (1-3 business days) before certificates can be issued. *Fill in all required details carefully - they must match official legal records.*

**Organization Name (\*)**: The full legal name of your organization. *Automatically filled from the selected organization. Verify it matches your official registration exactly*.

**Organization Unit**: The department or division within the organization (optional). *Leave blank if not applicable, or enter a relevant department name (e.g., 'IT Security', 'Operations').*

**Street Address 1 (\*)**: The first line of the organization's registered street address. *Automatically filled. Verify accuracy.*

**Street Address 2**: Second address line (optional, e.g., Suite or Floor number). *Fill in if applicable.*

**Country (\*)**: The country where the organization is registered. *Automatically filled from the validated organization record.*

**State / Province (\*)**: The state or province of the organization's address. *Automatically filled. Select from dropdown if required.*

**Locality (\*)**: The city or locality of the organization's address. *Automatically filled. Verify it is correct.*

**Postal Code / Post Office Box Number (\*)**: The postal/ZIP code of the organization's address. *Automatically filled. Verify accuracy.*

&#x20;

**Note - Organization Details Accuracy**&#x20;

*The organization details entered here must exactly match the information on official government or business registration documents (e.g., company registration certificate, articles of incorporation).*

The CA will verify these details during the validation process.

Discrepancies will cause delays or rejection of your application.

&#x20;

**Action**&#x20;

*After selecting your organization and confirming the details are accurate, click Next.*


---

# 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-ov-public-trust-certificates/phase-1-steps/step-3-organization-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.
