# User Profile

**Objective:** The User Profile page is used to view or update user details like name, gender, email, phone number, and profile pic. 

A user profile is created when the user registers the application for the first time. 

## Types of User Profiles <a href="#types-of-user-profiles" id="types-of-user-profiles"></a>

* **Citizen:** A citizen is a basic user who uses the application to perform basic tasks including
  * creating applications, properties, etc
  * viewing all applications, properties, etc
  * payments
* **Employee:** An employee is a user linked to the organization and is more privileged than the citizen and can perform the following tasks
  * creating applications, properties, etc
  * viewing all applications, properties, etc
  * payments
  * and many more

## **Technical Implementations**

Technical Implementations of the user profile code link: <https://github.com/egovernments/DIGIT-Dev/blob/master/frontend/micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/Home/UserProfile.js>

## **API Call Role Action Mapping**

| **API**                 | **ACTION ID** | **ROLES**            |
| ----------------------- | ------------- | -------------------- |
| `/filestore/v1/files`   |               | `PTCEMP, CITIZEN`    |
| `/user/profile/_update` |               | `PTCEMP, CITIZEN`    |
| `user/password/_update` |               | `ObOPTCEMP, CITIZEN` |


---

# 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://docs.digit.org/local-governance/deploy/configure-digit/configuring-digit-services/common-ui-docs/user-profile.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.