> 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/view-edit-organisation-details.md). # View/Edit Organisation Details ## Scope View/ Edit Organization’s Details - PII data to be masked. ## **Actor** Employee ## **Details** 1. Change in View/ Edit Organization is required to implement data privacy. 2. PII and sensitive information to be masked for all other roles other than “**View\_ORG\_Unmasked**”. 3. The format of masking is as given below. 1. Door No. - **The first letter is shown, and the rest is masked.** **e.g. 101A/2 → 1\*\*\*\*\*.** 2. Street Name - **The first letter is shown, and the rest is masked.** **e.g.** Gandhi Marg → G\*\*\*\*\*\*\*\*g. 3. Locality - **The first letter is shown, and the rest is masked.** **e.g.** Manohar Nagar → M\*\*\*\*\*\*\*\*\*\*\*r. 4. Mobile Number - The first 8 digits are masked, rest are displayed. e.g. 8888888888 → \*\*\*\*\*\*\*\*\*\*88. 5. Email ID - The first, last and domain are displayed, rest all are masked. e.g. → n\*\*\*\*\*\*\* 6. Account number - Only last 4 digits are displayed, rest all are masked with asterisk. e.g. 321004567621 → \*\*\*\*\*\*\*\*7621. 7. IFSC - The first 4 and last 2 digits are displayed, rest are masked. e.g. ICIC0000047 → ICIC\*\*\*\*\*47. 8. Branch Address - 1. Street number and specific street details are masked. 2. The district name is partially masked. 3. The city, state, and postal code remain visible. 9. PAN - The first 3 and Last 2 digit are displayed. rest are masked. BNQNS7208B → BNQ\*\*\*\*\*\*8B. 10. GSTIN - The first 3 and Last 2 digit are displayed. rest are masked. 4. The details shown masked for the role other than **View\_ORG\_Unmasked.** 5. For the user having role “**View\_ORG\_Unmasked**” information displayed is unmasked. ## User Interface View {% embed url="" %} Edit {% embed url="" %} ## Acceptance Criteria 1. Organization contact person PII and sensitive data are to be masked while displayed based on role. 2. A user having the role permission for “**View\_ORG\_Unmasked**” can see the details unmasked. 3. A user having a role permission other than “**View\_ORG\_Unmasked**” and view the details masked without an option to unmask it. --- # 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/view-edit-organisation-details.md?ask=&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.