> For the complete documentation index, see [llms.txt](https://whiteklay.gitbook.io/virtual-data-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whiteklay.gitbook.io/virtual-data-assistant/how-to-guides/data-governance.md).

# Data Governance

Data governance is the practice of managing and controlling data to ensure its accuracy, quality, security, and accessibility throughout its lifecycle. Effective data governance establishes policies, procedures, and standards to manage data assets, ensuring they are reliable and trusted. It plays a critical role in compliance, risk management, and decision-making processes within an organization.

### **The Importance of Role-Based Access Control (RBAC) in Data Governance**

Role-Based Access Control (RBAC) is a method of regulating access to data based on the roles of individual users within an organization. By assigning permissions to specific roles rather than individual users, RBAC simplifies the management of user privileges and enhances data security. Integrating RBAC into data governance ensures that only authorized personnel can access, modify, or manage data according to their roles and responsibilities.

### **Implementing RBAC in VDA** <a href="#implementing-rbac-in-vda" id="implementing-rbac-in-vda"></a>

1. Login as SUPERADMIN user
2. Move to Permissions Tab
3. In the Permissions Page, Select the "Role Name" then from the below dropdown API list select the "Mappings Applies Selected Role" and click on submit.
4. Below the role selection, you will see a list of available permissions and mappings.
5. Select the appropriate permissions that you want to apply to the chosen role.&#x20;

<img src="https://803373986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEZ25VHhdl67JelwmVtBp%2Fuploads%2F5upYm5y6eZckJEjqgBOC%2Funknown.png?alt=media&amp;token=5807e913-a80b-47eb-9f47-1853ee36451c" alt="" height="302" width="664">

<img src="https://803373986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEZ25VHhdl67JelwmVtBp%2Fuploads%2FUFFvSOinXNXvo9NpkQcU%2Funknown.png?alt=media&amp;token=7fff7413-e2a0-430d-93c3-ff2236202108" alt="" height="305" width="664">

7. Click on Submit to save the changes.
8. After this, users should only be able to see pages and perform actions for which they are explicitly authorized.

### Key Benefits&#x20;

1. **Enhanced Security:** By restricting data access based on roles, RBAC minimizes the risk of unauthorized access and potential data breaches.&#x20;
2. **Compliance and Auditability:** RBAC helps organizations comply with regulatory requirements by providing clear audit trails of who accessed and modified data.&#x20;
3. **Improved Efficiency:** Simplifies the process of managing user permissions, especially in large organizations with complex data environments.&#x20;
4. **Scalability:** Facilitates easier administration of access controls as organizations grow and roles evolve.&#x20;
5. **Risk Mitigation:** Reduces the likelihood of human error and misuse of data by ensuring that users only have access to data necessary for their roles.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whiteklay.gitbook.io/virtual-data-assistant/how-to-guides/data-governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
