> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/data-access/dam-supported-connectors/tableau.md).

# Tableau

## Introduction

The Data Access Management (DAM) feature provides a structured, catalog-like view of users, roles, and group permissions across various data objects. This enables administrators or source system owners to gain clear visibility into access rights and manage permissions effectively.

This section describes how Data Access Management works for Tableau, detailing how organizations can sync and explore metadata, examine permissions assigned to users, roles, and groups, and capture audit logs of all crawled entries.

For more details, refer to the [Data Access Management - DDA](/release8.3/data-access/data-access-management.md).

{% hint style="info" %}
DAM functionality may vary depending on the capabilities of the source system.
{% endhint %}

### Tableau Metadata Cataloging

| Source Object | Attribute                   |
| ------------- | --------------------------- |
| Sites         | Site Name                   |
| Sites         | Users                       |
| Sites         | Group                       |
| Sites         | Users & Groups Associations |
| Sites         | Site Administrators         |
| Sites         | Audit                       |
| Projects      | Top Level Project           |
| Projects      | Sub Projects                |
| Projects      | Project Descriptions        |
| Projects      | Owners                      |
| Projects      | Audit                       |
| Workbook      | Workbook Name               |
| Workbook      | Workbook type               |
| Workbook      | Owners                      |
| Workbook      | Audit                       |
| Datasource    | Datasource Name             |
| Datasource    | Datasource type             |
| Datasource    | Owners                      |
| Datasource    | Audit                       |
| Views         | View Name                   |
| Views         | View Type                   |
| Views         | Audit                       |

### Tableau Permissions

| Tableau Permissions Cataloging | Availability |
| ------------------------------ | :----------: |
| User-Level                     |       ✅      |
| Group-Level                    |       ✅      |
| Project-Level                  |       ✅      |
| Workbook-Level                 |       ✅      |
| Datasource-Level               |       ✅      |
| Views-Level                    |       ✅      |
| Effective Permissions          |       ❌      |

{% hint style="info" %}
Due to the limitations of the Tableau APIs, the Application currently cannot catalog effective permissions*.*
{% endhint %}

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA


---

# 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.ovaledge.com/release8.3/data-access/dam-supported-connectors/tableau.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.