> For the complete documentation index, see [llms.txt](https://usermanuals.geojit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanuals.geojit.com/flip-mobile/more/profile.md).
# Profile
Your complete **"Profile"** details such as **Contact Details, Bank Details, Client Details, Power of Attorney Status,** and **Active & Inactive Segments and Products** are displayed here.
### How to open the Profile page
To open the **"Profile"** page, follow these steps:
* Locate the **"More" Icon**
at the bottom of the page.
* Click on the **"More" Icon**
to go to the **More page.**
* You can see your **"Name"** and **"Trade Code"** at the top of the page.
* Click on your **Name / "Arrow" Icon**
at the left-hand side**.**
* This will redirect you to the **"Profile" page**.
* Click on the **"Back Arrow" Icon**
at the top-right hand side to go back to the **More page.**
* You can see details like your - registered email, mobile number, account number, customer ID, DP client ID, DP ID, DP, UCC, **password expiry**, KRA status, PoA/DDPI, active segments, inactive segments, active products and inactive products.
---
# 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://usermanuals.geojit.com/flip-mobile/more/profile.md?ask=&goal=
```
`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.
