> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/functional-overview/end-user-guide/interface-overview.md).

# Interface Overview

## Introduction

This guide provides an overview of the Inji Verify user interface based on the reference implementation. It covers the key sections and features available to end users for credential verification workflows.

For hands-on exploration and testing, you can refer to the Inji Verify collab environment.

## **Header Section**

### **Home**

### **Verify Credentials**

* The Verify Credentials Page will showcase two main features of Inji Verify that is "Upload QR Code" and "Scan the QR Code".

<figure><img src="/files/X88cGlsw0CIVgGvQ7Mdy" alt="" width="200"><figcaption></figcaption></figure>

### **Help**

The Help section includes three sub-sections or sub-menus:

* **Contact Us**: This directs you to our MOSIP Community where you can write to us with any queries related to Inji Verify or general inquiries.
* **Documentation**: This directs you to the Inji Verify documentation page for detailed information about Inji Verify.
* **FAQ**: This section is still under development.

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

### **Language Selection**

Language dropdown is provided for verifier to select a language of his interest for better usability . The languages currently supported are: Portuguese, Spanish, French, English, Arabic, Tamil, Khmer, Hindi and Kannada.

<figure><img src="/files/56sfhof8Qof7MPMB1SFu" alt=""><figcaption></figcaption></figure>


---

# 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.inji.io/inji-verify/functional-overview/end-user-guide/interface-overview.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.