> 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-muster-roll-details.md).

# Display Muster Roll Details

## Scope

Data Privacy: Changes in muster roll (AADHAAR to be removed)

## **Actor**

Employee

## **Details**

1. Change in View/ Edit Muster Roll is required to implement data privacy.
2. The following details are to be removed from muster roll View and Edit Pages and PDF.
   1. Account Number
   2. IFSC
   3. AADHAAR
3. Wage seeker ID should be a hyperlink to view the beneficiary details.
4. PII and sensitive information are displayed masked/unmasked based on the role of the logged-in user.
5. Rest remains the same as the existing muster roll.

## User Interface

{% embed url="<https://www.figma.com/design/M2P3O9WlKtxuLCjQKxLLDg/DIGIT-Works>" %}

## Acceptance Criteria

1. Sensitive account information like IFSC and AADHAAR is to be removed from the muster roll view, edit, and PDF.
2. Wage seeker ID to be available as a hyperlink.
3. Wage seekers' details are displayed as masked/unmasked based on the role of the logged-in user.


---

# 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-muster-roll-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.