> For the complete documentation index, see [llms.txt](https://docs.esignet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esignet.io/home/esignet/esignet-authentication/test/end-user-guide/health-portal/login-with-qr-code.md).
# Login with QR code (Inji)
{% hint style="success" %}
**Prerequisites:**
* Residents should have the Inji app installed on their mobile devices.
* They should have credentials downloaded and should have activated it for online login. To know how to activate the VC for online login, refer [Inji User Guide](https://docs.mosip.io/inji/inji-wallet/backend-services/mimoto#wallet-binding).
{% endhint %}
1\. Resident launches the relying party's portal and clicks on ***Sign In with eSignet***.
Health Portal Home Page
2\. Resident selects the ***Login with Inji Mobile App*** option.
Login with Inji
3. Now, the resident can scan the QR code displayed on the portal using Inji (on their mobile device).
Inji QR code
As seen below, the authentication is in progress.
4. On Inji, the resident can see the VC that is activated for online login. Select the VC and click ***Verify***.
5. After clicking on ***Verify***, the resident is asked to perform face authentication. On successful authentication, the **Consent** screen is displayed.
6. Here, the residents can provide their consent and click ***Allow***. A successful message is displayed on Inji.
7. The resident can log into the relying party portal and view their details on the user profile page.
---
# 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.esignet.io/home/esignet/esignet-authentication/test/end-user-guide/health-portal/login-with-qr-code.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.
