# For Users

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

**User Verification**:

&#x20;Users can submit their KYC (Know Your Customer) details such as their name and user ID to get verified on the platform. This helps in ensuring that only legitimate users are allowed access to certain features or services.

**Identity Verification**:

&#x20;The contract verifies the identity of users by checking if their user ID already exists in the system. This prevents duplicate or fraudulent accounts from being created.

**Verification Status**:

&#x20;Users can check the verification status of their KYC data by querying the contract. This provides transparency and allows users to ensure that their information is correctly processed.

**Signer Verification**:

&#x20;Users who are authorized to verify KYC data can use the `verifyKYC` function to mark the submitted data as verified. This ensures that only authorized entities can approve KYC submissions.

**Querying KYC Data**:&#x20;

Users can retrieve their KYC details stored on the blockchain by calling the `getKYCDetails` function. This allows them to access their verified information whenever needed.

**Retrieving KYC Data by Signer**:&#x20;

Users can also retrieve KYC data associated with a specific signer address by calling the `getKYCDataBySigner` function. This is useful for platforms or services where multiple users may be associated with the same signer address.


---

# Agent Instructions: 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:

```
GET https://kuzhanthaivelus-organization.gitbook.io/kyc3-sdk/use-cases/for-users.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.