# Privileges

Catalog privileges offer a system for managing authentication and access across catalog, database, table, and column levels. Privilege is a set of rules or policies used to ensure only the intended users have permission to access data. 

{% hint style="info" %}
Upon creating a catalog, access is initially restricted by default, employing the **Deny All** privileges for all users. This approach aligns with governance and security protocols, guaranteeing that essential access is meticulously granted.
{% endhint %}

{% hint style="info" %}
For a user to be able to access, add, update and modify catalog privileges, The [DataAdmin role](/product-documentation/access-control/roles.md) must be assigned, ***including SuperAdmins.***

For a user to be able to access query editor, The [DataAnalyst role](/product-documentation/access-control/roles.md) must be assigned, ***including SuperAdmins.***

***Please be sure to use it cautiously, as it provides access to*** [***read potentially sensitive data***](/product-documentation/faqs/security.md#what-data-other-data-moves-outside-the-data-plane)***.***
{% endhint %}

e6data offers three types of privileges that can be applied to data objects:

1. [Access Control](/product-documentation/catalogs/privileges/access-control.md)
2. [Column Masking](/product-documentation/catalogs/privileges/column-masking.md) 
3. [Row Filter](/product-documentation/catalogs/privileges/row-filter.md) 

{% embed url="<https://www.loom.com/share/5bce51d2a9f34a44bf31308d7436964f?sid=a1eb3930-743d-44fa-a0b1-a8b50313a356>" %}


---

# Agent Instructions: 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:

```
GET https://docs.e6data.com/product-documentation/catalogs/privileges.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.