> 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/deployment/release-notes.md).

# Release Notes

MUKTASoft v2.2

## Release Summary

The MUKTASoft v2.2 release introduces a series of data privacy-related enhancements and changes to ensure compliance, security, and user trust in managing sensitive information.

## Release Highlights

1. A privacy policy notice has been added to the login page, requiring user acceptance before proceeding.&#x20;
2. Bank account details have been removed from the "View Bill Details" page.&#x20;
3. Bank account details and Aadhaar numbers are no longer displayed on the "View Muster Roll Detail" page for both web and mobile applications.&#x20;
4. Account numbers and IFSC codes are masked for users without the required access permissions.&#x20;
5. In the "View and Edit Wage Seeker's Details" section, all personally identifiable information (PII) is masked for unauthorized users.&#x20;
6. In the "View and Edit Organization's Details" section, all PII is masked for users without access rights.&#x20;
7. PII has been removed or masked in the "View Engaged Wage Seeker Details" section.&#x20;
8. Organization profile pages now have masked PII data.&#x20;
9. On the "Track Attendance" page, PII has been removed or masked.&#x20;
10. When searching for wage seekers to engage in projects, the guardian's name is now displayed alongside the wage seeker's name.&#x20;
11. PII and sensitive information have been removed from the additional details in each service.

## New Features/Enhancements

No new feature has been added.

## Bug Fixes

None

## Known Issues

None

## Upcoming Release Features

None


---

# 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/deployment/release-notes.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.
