> For the complete documentation index, see [llms.txt](https://docs.elkyc.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elkyc.com/home/review-data/applicant-profile.md).
# Applicant Profile
The Applicant Profile section serves as the central hub for managing and reviewing key information about each applicant. This feature enables you to efficiently access, verify, and monitor all data.
### Overview
* From the Sidebar Menuclick on `Verifications` and go to `Applicants` tab:
* Click on the `Applicant` to open the profile and see the details. The table view offers a clear and concise summary of applicant information:
***
As illustrated in the screenshot, this view is organized into several key sections:
1. **Applicant Header**
**Applicant Name and Status**: Displays the applicant's full name and the current status of their verification.
**Profile Picture**: Provides a visual identification of the applicant.
**External User ID**: A unique identifier specific to this applicant within your system.
**Reviewer Assignment**: Shows the currently assigned reviewer. The reviewer can be changed using the dropdown menu.
**Approve/Decline Options (in case the reviewer is assigned)**: Allows the reviewer to either approve or decline the applicant’s profile based on the verification results.
***
2. **Info and Comments Tabs**
**Info Tab**: Displays key applicant details organized into several categories:
* **Applicant IDs**: Includes the External User ID and Applicant ID for tracking and integration purposes.
* **Personal Info**: Lists the applicant's date of birth, location, and IP address. Additional fields like email and telephone number may also be displayed.
* **Verification Info**: Contains the date and time of the application, the platform used (e.g., WEB), and the current status of the application.
* **Device Info**: Shows details about the device used during the application process, including location data (Latitude, Longitude), browser type, version, and user agent string.
**Comments Tab**: A section where reviewers can add and view notes or comments related to the applicant's profile.
***
3. **Verification Tracker**
**Tracker**: A visual progress bar showing the stages of the verification process, such as Document Check, Liveness, Selfie Capture, and Face Match. The progress tracker helps reviewers quickly assess which steps have been completed and which are pending or failed.
{% hint style="info" %}
Also, you can [restart](/home/verify-your-users/restart-the-verification-flow.md), [change](/home/verify-your-users/change-the-verification-flow.md) the flow or [request](/home/verify-your-users/request-additional-information.md) additional information from the tracker.
{% endhint %}
***
4. **Verification Steps Details**
These sections allow the reviewer to delve into specific verification tasks, providing detailed insights into the results of each step.
Description of each section is provided in the next chapters.
***
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.elkyc.com/home/review-data/applicant-profile.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
