> For the complete documentation index, see [llms.txt](https://docs.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neevcloud.com/neevcloud-account/getting-started-with-neev-account/create-and-activate-neevcloud-account/customer-validation-process-faqs.md).

# Customer Validation Process FAQs

### Why is customer validation required for customers?

As per the recent directives from [CERT-In,](https://www.cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf) all Data Centres, Virtual Private Server (VPS) providers, and Cloud Service providers must now maintain verified information, including names, addresses, and other relevant details, for their subscribers. Consequently, to comply with the regulatory guidelines, we need to validate and keep this information up-to-date.

### Is it possible to assign someone within the team/company to carry out customer validation?

Yes, the Primary contact/Admin user can assign any user in a team to perform customer validation. but the user should be Autherize from the organization,

### Do all users in the NeevCloud Account need to complete customer validation?

Yes, all users in the NeevCloud Account need to complete customer KYC validation.


---

# 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.neevcloud.com/neevcloud-account/getting-started-with-neev-account/create-and-activate-neevcloud-account/customer-validation-process-faqs.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.
