> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/trust-access/data-access-governance/object-access-policies.md).

# Object Access Policies

#### **Object Access Policies in TrustLogix**

**Object Access Policies** are **RBAC (Role-Based Access Control) policies** designed to manage permissions for **system objects** (e.g., accounts, warehouses) and **database objects** (e.g., databases, schemas, tables, views). These policies ensure **controlled access** based on predefined roles and permissions.

**Types of Object Access Policies:**

1. **Privilege Template-Based Policies**
   * Standardized role and privilege assignments for system and database objects.
   * Ensures consistent access control across environments.
2. **Tag-Based Policies**
   * Leverages **data classification tags** to enforce access restrictions.
   * Allows automated policy application based on **data sensitivity** or **compliance requirements**.
3. **Database, Schema, and Table-Level RBAC Policies**
   * Grants or restricts access **at a granular level**, ensuring least-privilege access.
   * Supports **role-based access enforcement** for specific objects like tables and views.

By defining **Object Access Policies**, organizations can enforce **fine-grained access control**, reduce security risks, and streamline **data governance**.


---

# 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.trustlogix.io/trust-access/data-access-governance/object-access-policies.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.