> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/data-protection-and-privacy/display-engaged-wage-seeker-details.md).

# Display Engaged Wage Seeker Details

## Scope

Data Privacy: Engage Wage Seeker changes

## **Actor**

CBO

## **Details**

1. Mobile number to be removed from display of engaged wage seekers.
2. The details are displayed as given below.
   1. Name
   2. Father/ husband’s name
   3. Address
3. The details given above are displayed only in cases where the role permission is “**View\_WS\_Unmasked**”.
4. For the other roles, the details given above are displayed masked.
5. The masking format is given below.
   1. Name - displayed unmasked.
   2. Father/ husband name: ***The first letter of each part of the name, followed by asterisks. (A\*\* B\*\*\*\*\*\*)***
   3. Address
      1. Door No. - **The first letter is shown, and the rest is masked.**
      2. Street name - The first letter is shown, and the rest is masked.
      3. Locality - The first letter is shown, and the rest is masked.
      4. Ward - The first letter is shown, and the rest is masked.
      5. City - The first letter is shown, and the rest is masked.

## User Interface

{% embed url="<https://www.figma.com/design/M2P3O9WlKtxuLCjQKxLLDg/DIGIT-Works?node-id=13294-27030&node-type=frame>" %}

## Acceptance Criteria

1. Mobile number is removed from engaged wage seekers display.
2. PII and sensitive information displayed masked for roles with permissions other than **View\_WS\_Unmasked**.
3. For the user(s) having role permissions for **View\_WS\_Unmasked** PII and sensitive details are displayed unmasked.


---

# 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.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/data-protection-and-privacy/display-engaged-wage-seeker-details.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.