> For the complete documentation index, see [llms.txt](https://docs.pockethrms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pockethrms.com/faqs/cloud-portal/ess-settings/profile-info/profile-settings.md).

# Profile Settings

### 1. How to make date of birth (DOB) and date of joining (DOJ) non-editable for employees in ESS?

**Step 1**: Log into the cloud portal, go to the ‘ESS Settings’ menu and under the ‘Profile Info’ tab, click on the ‘Profile Settings’ subtab.

![](https://4282324958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXep_PEmh8mDPVWj49x%2Fuploads%2FBTA3jsOYFB4K6nyI4K1L%2F0.png?alt=media)

**Step 2**: Under the ‘View Only’ column, select the radio button for the ‘Date of Birth’ and ‘Date of Joining’ options, make other required changes and scroll down to click on the ‘Update’ button.

![](https://4282324958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXep_PEmh8mDPVWj49x%2Fuploads%2FO06QMFJsJg0laj3Hfp8d%2F1.png?alt=media)

**Path**: Cloud Portal > ESS Settings > Profile Info > Profile Settings >tick radio buttons under ‘View Only’ column for respective fields > Update

**Link**:

<https://cloud.pockethrms.com/Settings/Employee/ESSIndex?module=Profile&submodule=ProfileSetting>

For any queries, contact <support@pockethrms.com>

### 2. How to remove the employee access from the ESS portal for tax regime change?

To disable employee access for changing the tax regime kindly follow the path below:

**Path:** Cloud login > Go to ESS Settings > Profile Info > Profile Setting > In Employee details disable the ITax Regime Type > scroll down > Update.

**Step 1:** Log in to the **Cloud portal** and navigate to the **‘ESS Settings’** module.

<figure><img src="https://content.gitbook.com/content/-MXep_PEmh8mDPVWj49x/blobs/Bmt8jtuKLEASF0f5fTI5/Unknown%20image" alt=""><figcaption></figcaption></figure>

**Step 2:** Select the **‘Profile Info’** tab and then click on **‘Profile Setting’**.

![](https://content.gitbook.com/content/-MXep_PEmh8mDPVWj49x/blobs/epdOwzPAWOBOYsiYFYH1/Unknown%20image)

**Step 3:** Locate the **‘Employee Details’** section where various profile fields are listed, Find the **‘ITax Regime Type’** option in the list, **disable** this option (usually by unchecking the box or toggling it to 'No') to prevent it from appearing or being editable.

![](https://content.gitbook.com/content/-MXep_PEmh8mDPVWj49x/blobs/S7g14RQnm9NuKCEbNrLG/Unknown%20image)

**Step 4:** Scroll down to the bottom of the page and click the **‘Update’** button to save the changes.

![](https://content.gitbook.com/content/-MXep_PEmh8mDPVWj49x/blobs/MH4NbEN8AKeyv2FhTzVX/Unknown%20image)

**Link:**<https://cloud.pockethrms.com/Settings/Employee/ESSIndex?module=Profile&submodule=ProfileSetting>

For any queries, contact <support@pockethrms.com>


---

# 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.pockethrms.com/faqs/cloud-portal/ess-settings/profile-info/profile-settings.md?ask=<question>&goal=<user_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.