> For the complete documentation index, see [llms.txt](https://docs.e6data.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/product-documentation/faqs/catalog-privileges.md).

# Catalog Privileges

<details>

<summary>Can users define policies at different levels of granularity?</summary>

Yes, users can define privileges at catalog, schema, table, and column levels, providing fine-grained control over data access.

</details>

<details>

<summary><strong>Are privileges applied to individual users or groups?</strong></summary>

Currently, privileges can be defined for users and groups.

</details>

<details>

<summary><strong>What types of privileges can be defined?</strong></summary>

Currently, users can define access privileges only. Row filtering and column masking privileges are not supported initially but are planned for future releases.

</details>

<details>

<summary><strong>How do I modify a privilege?</strong></summary>

Currently, the Data Admin can modify the privilege by selecting the relevant privileges in the catalog privileges screen and updating the details of the privilege. The updated privileges will start reflecting in 60-90s seconds.

</details>

<details>

<summary><strong>How are unauthorized queries handled?</strong></summary>

Unauthorized queries are cancelled during execution, and users receive appropriate error messages. Additionally, query history reflects denied access for transparency and auditability.

</details>

<details>

<summary><strong>What happens if a new user is added without specified privileges?</strong></summary>

In a governed cluster, if a new user is added without specified privileges, they are assumed to have access to no data. It is essential to add privileges for new users or add new users to certain groups to avoid query failures for them.&#x20;

</details>

<details>

<summary><strong>What are the benefits of catalog privileges for users?</strong></summary>

This feature simplifies data access management, enhances data security, and provides transparent control over access policies, ensuring compliance for users.

</details>

<details>

<summary><strong>How does the system handle performance implications when applying access privileges to large datasets or complex queries?</strong></summary>

The system is designed to apply access privileges efficiently during query execution without significant performance overhead.

</details>


---

# 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://docs.e6data.com/product-documentation/faqs/catalog-privileges.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.