> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tableau Connector

> Connect Tableau dashboards to Collate with our comprehensive connector guide. Setup instructions, configuration options, and metadata extraction steps.

export const ConnectorDetailsHeader = ({name, icon, stage, availableFeatures, unavailableFeatures = [], availableFeaturesCollate = []}) => {
  const showSubHeading = availableFeatures?.length > 0 || unavailableFeatures?.length > 0 || availableFeaturesCollate?.length > 0;
  const totalAvailableFeatures = [...availableFeatures || [], ...availableFeaturesCollate || []];
  return <div className="container">
      <div className="Heading">
        <div className="flex items-center gap-3">
          {icon && <div className="IconContainer">
              <img src={icon} alt={name} noZoom className="ConnectorIcon" />
            </div>}
          <h1 className="ConnectorName">{name}</h1>
          <span className={`StageBadge ${stage === 'PROD' ? 'prod' : 'beta'}`}>
            {stage}
          </span>
        </div>
      </div>
      {showSubHeading && <div className="SubHeading">
          <div className="FeaturesHeading">Feature List</div>
          <div className="FeaturesList">
            {totalAvailableFeatures.map(feature => <div className="FeatureTag AvailableFeature" key={feature}>
                ✓ {feature}
              </div>)}
            {unavailableFeatures.map(feature => <div className="FeatureTag UnavailableFeature" key={feature}>
                ✕ {feature}
              </div>)}
          </div>
        </div>}
    </div>;
};

<ConnectorDetailsHeader icon="/public/images/connectors/tableau.webp" name="Tableau" stage="PROD" availableFeatures={["Dashboards", "Charts", "Lineage", "Owners", "Datamodels", "Tags", "Projects", "Column Lineage", "Usage", "Reverse Metadata (Collate Only)"]} unavailableFeatures={[]} />

This section provides guides and references to use the Tableau connector.
Configure and schedule Tableau metadata and profiler workflows from the Collate UI:

* [Requirements](#requirements)
* [Entity Mapping](#entity-mapping)
* [Metadata Ingestion](#metadata-ingestion)
* [Enable Security](#securing-tableau-connection-with-ssl-in-collate)
* [Lineage](#lineage)
* [Troubleshooting](/ai-2-0/connectors/dashboard/tableau/troubleshooting)
* [Reverse Metadata](#reverse-metadata)

## Requirements

To ingest Tableau metadata, minimum `Site Role: Viewer` is required for the Tableau user.
To create lineage between Tableau dashboards and any database service via the queries provided from Tableau Metadata API, enable the Tableau Metadata API for your Tableau server.
For more information, see [Get Started with the Metadata API](https://help.tableau.com/current/api/metadata_api/en-us/docs/meta_api_start.html).

<Tip>
  **Tip**:

  * If using a **default site** on Tableau Server, leave the **Site URL** and **Site Name** fields **blank** in the ingestion configuration.
  * Ensure that the **Metadata API** is enabled for the user performing the ingestion. If it is not enabled, ingestion may fail. Follow the official Tableau documentation to [enable the Metadata API](https://help.tableau.com/current/api/metadata_api/en-us/docs/meta_api_start.html#enable-the-tableau-metadata-api-for-tableau-server).
  * The minimum required role to retrieve owners is Site Admin Explorer.
</Tip>

<Tip>
  **Tip**:

  * As of Collate versions `1.7.4` and `1.7.5`, the `siteUrl` field has been removed from the Tableau connector configuration. This change was intentional, as confirmed in the release commit.
  * To connect to a non-default Tableau site, use the `siteName` field instead. The Tableau Python SDK does not require `siteUrl` for authentication.
  * Ensure the `siteName` field is correctly populated (do not use `*`) to enable successful metadata ingestion for multi-site Tableau environments.
</Tip>

### Source Tables and Lineage

<Warning>
  **Important**:
  **Table lineage requires** the ingestion account to have the **View** capability on the external assets in Tableau Catalog, granted directly or derived. For any asset it cannot view, Tableau returns the source table with its table and database names removed, keeping only internal identifiers, and reports no error. Those tables are skipped without a message, so **no lineage is created between them and the data models that use them**. Assets the account can view are unaffected, and dashboards, charts and data models are still ingested either way.
</Warning>

Grant the ingestion account **View** on the affected external assets in Tableau Catalog, or use an account that already holds it. A Viewer or Explorer site role alone is not enough for Collate to build table lineage. For the steps, see [Manage Permissions for External Assets](https://help.tableau.com/current/server/en-us/dm_perms_assets.htm) in the Tableau documentation.

## Entity Mapping

The Tableau connector maps Tableau assets to Collate entities as follows:

| Tableau Asset                                                    | Collate Entity    | Description                                                                             |
| ---------------------------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------- |
| **Workbooks**                                                    | **Dashboard**     | Tableau workbooks are mapped to Collate Dashboard entities.                             |
| **Views** (worksheets, dashboard views, stories—all sheet types) | **Chart**         | All Tableau views are mapped to Collate Chart entities, regardless of their sheet type. |
| **Data Sources** (embedded and published)                        | **Data Models**   | Tableau data sources are mapped to Collate Data Model entities.                         |
| **Projects**                                                     | **Project field** | The Tableau project name is stored in the project field of the Dashboard.               |

### Example Structure

**Tableau Structure:**

```
Project: Sales Team
└── Workbook: Sales Analysis
    ├── Dashboard: Revenue Overview (sheetType="dashboard")
    ├── Worksheet: Monthly Sales (sheetType="worksheet")
    └── Story: Sales Story (sheetType="story")
```

**Collate Structure:**

```
Dashboard: "Sales Analysis" (Project: "Sales Team")
├── Chart: "Revenue Overview"
├── Chart: "Monthly Sales"
└── Chart: "Sales Story"
```

This mapping ensures that:

* Tableau workbooks appear as Collate dashboards.
* All views (worksheets, dashboard views, stories) appear as charts under that dashboard.
* Tableau project names are preserved in the project field.
* URLs point directly to the specific views.

## Metadata Ingestion

To ingest metadata from Tableau, you need to create a service connection. The service connects Tableau with Collate. Once you create a service, Collate automatically starts ingesting metadata.

### Step 1: Add New Service

1. In the left navigation, click **Connections**.
2. On the **Connections** page, click **Add New Service**.

<img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/add-new-service.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=733cef1141ef13d318634aa9f407eb2b" alt="Add New Service" width="2992" height="1256" data-path="public/images/ai-2.0/connectors/metadata-ingestion/add-new-service.png" />

### Step 2: Select a Service and Connector

From the service type dropdown, select **Dashboard Services**, then click the **Tableau** connector tile.

<img src="https://mintcdn.com/collatedocs/kTp2dTyiNAX4Np5A/public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/select-service/tableau.png?fit=max&auto=format&n=kTp2dTyiNAX4Np5A&q=85&s=05486f2239bb92a8fd3a47067e7912b1" alt="Select Service" width="1972" height="1470" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/select-service/tableau.png" />

### Step 3: Add Service Name and Description

* Enter a unique, descriptive **Service Name**. Collate identifies services by their service name. Enter a name that distinguishes this deployment from other Tableau services you are ingesting metadata from.
* Optional: Enter a **Description** for the service.

<img src="https://mintcdn.com/collatedocs/kTp2dTyiNAX4Np5A/public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/service-name/tableau.png?fit=max&auto=format&n=kTp2dTyiNAX4Np5A&q=85&s=3dfcbb9fbd968a6c5ebd71276b644a98" alt="Add New Service Name" width="1494" height="856" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/service-name/tableau.png" />

<Note>
  **Note**: The service name cannot be changed after it is set.
</Note>

### Step 4: Configure Connection Options

Specify where ingestion runs, provide your source credentials, and verify the connection.

#### Select Ingestion Runner

Select an **Ingestion Runner**: the runner where the ingestion pipeline will execute.

<img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/select-ingestion-runner.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=1249f828648614445e8a976ea1933487" alt="Add Name and Select Ingestion Runner" width="1444" height="506" data-path="public/images/ai-2.0/connectors/metadata-ingestion/select-ingestion-runner.png" />

#### Enter Connection Details

Enter the connection details for Tableau. The right-hand panel in the UI displays inline help for each field.

<img src="https://mintcdn.com/collatedocs/VsJxWKWlvReeFtlo/public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/connection-details/tableau.png?fit=max&auto=format&n=VsJxWKWlvReeFtlo&q=85&s=acde9fe7ddb13375344f1198eb703bc0" alt="Configure Service Connection" width="1442" height="1500" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/connection-details/tableau.png" />

* **Host and Port**: URL or IP address of your installation of Tableau Server.
* **Authentication Types**:
  1. Basic Authentication
  * Username: The name of the user whose credentials will be used to sign in.
  * Password: The password of the user.
  2. Access Token Authentication
  * Personal Access Token: The personal access token name. For more information, see [Personal Access Tokens](https://help.tableau.com/current/server/en-us/security_personal_access_tokens.htm).
  * Personal Access Token Secret: The personal access token value. For more information, see [Personal Access Tokens](https://help.tableau.com/current/server/en-us/security_personal_access_tokens.htm).
* **API Version**: Tableau API version. For a list of Tableau Server versions and their corresponding REST API and REST API schema versions, see [REST API Versions](https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_versions.htm).
* **Site Name**: This corresponds to the `contentUrl` attribute in the Tableau REST API. The `site_name` is the portion of the URL that follows the `/site/` in the URL.
* **Site URL**: If it is empty, the default Tableau site name will be used.
* **Environment**: The config object can have multiple environments. The default environment is defined as `tableau_prod`, and you can change this if needed by specifying an `env` parameter.
* **Pagination Limit**: The pagination limit will be used while querying the Tableau Graphql endpoint to get the data source information.

### Site Name and Site URL

The `Site Name` and `Site URL` fields behave differently depending on how your Tableau instance is deployed.

#### 1. Service Connection for Tableau Cloud

If you're connecting to a cloud Tableau instance, add the `Site Name` and `Site URL` with your site name.

#### 2. Service Connection for a Default Tableau Site

For a default Tableau site, the `Site Name` and `Site URL` fields should be kept empty.

#### 3. Service Connection for a Non-Default Tableau Site

For a non-default Tableau site, the `Site Name` and `Site URL` fields are required.

<Tip>
  **Tip**: If `https://xxx.tableau.com/#/site/MarketingTeam/home` represents the homepage url for your Tableau site, the `MarketingTeam` from the url should be entered in the `Site Name` and `Site Url` fields.
</Tip>

### Authentication Type

Tableau supports two authentication methods for the connector.

### 1. Basic Authentication

Basic authentication requires the username and password of the user signing in.

### 2. Access Token Authentication

Access token authentication requires the personal access token name and the personal access token value.
For more information, see [Personal Access Tokens](https://help.tableau.com/current/server/en-us/security_personal_access_tokens.htm).

#### Test Connection

Once the credentials have been added, click on **Test Connection** and **Save** the changes.

<img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/test-connection.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=3365cff7bb9d82c85a2ff9ab559d6f11" alt="Test Connection" width="1446" height="188" data-path="public/images/ai-2.0/connectors/metadata-ingestion/test-connection.png" />

### Step 5: Configure Ingestion Options

In the **What to Ingest** step, use filter patterns to control which assets Collate ingests from your dashboard service. Filter patterns use regular expressions applied to asset names.

#### How Filter Patterns Work

* **Include**: Add one or more comma-separated regular expressions. Collate ingests only assets whose names match at least one expression. Leave blank to include all assets.
* **Exclude**: Add one or more comma-separated regular expressions. Collate skips any asset whose name matches an expression. Leave blank to exclude nothing.

Rules match asset names using one of five expressions:

* **contains**: matches any name containing the value. For example, `sales` matches `my_sales_data` and `sales_2024`.
* **starts with**: matches names beginning with the value. For example, `prod_` matches `prod_db` and `prod_schema`.
* **ends with**: matches names ending with the value. For example, `_raw` matches `events_raw` and `logs_raw`.
* **is exactly**: matches the exact name only. For example, `analytics` matches only `analytics`.
* **matches regex**: matches names using a regular expression. For example, `^prod_.*_v\d+$` matches `prod_events_v1`.

When both Include and Exclude are set, Exclude takes priority.

<Tip>
  **Tip**: Leave all filter patterns empty to ingest all dashboards, charts, and data models available in the source.
</Tip>

**Filter Options**

The Dashboard, Chart, and Data Model sections each include the following filter options:

* **Dashboard**: Controls which dashboards Collate ingests from the source.
* **Chart**: Controls which charts within the ingested dashboards are included.
* **Data Model**: Controls which data models are included in metadata ingestion.

Each section provides the following controls:

* **Scan Mode**: You can choose between the following scan modes:
  * **Scan all**: Ingests every asset of that type the connector can access. This is the default.
  * **Only specific**: Enables include rules so only assets matching at least one rule are ingested.
* **Exclude system toggle**: Use this toggle to automatically filter out system-reserved names defined by the connector—for example, **Exclude system databases** for the Databases section.
* **Always exclude**: Add permanent exclusion rules (shown in red). Assets matching these rules are never ingested, regardless of include rules.
* **Preview**: Shows a real-time summary of what will be in scope based on your current rules.
* **Include rules** *(available only in **Only specific** mode)*: Click **+ Add** to define a rule. Added rules appear as chips; an asset is included if it matches any rule.

<Tip>
  **Tip**: If [AutoPilot](/ai-2-0/admin-guide/applications/autopilot) is enabled, usage tracking, data lineage, and other downstream workflows start automatically after the first metadata ingestion completes.
</Tip>

### Step 6: Create & Deploy

Click **Create & Deploy** to deploy the agent and start the first metadata ingestion run. Collate saves the service configuration and immediately begins pulling metadata from the source.

To monitor ingestion progress or view the service you just added, go to **Connections** in the left navigation and select your service.

## Configure Metadata Agent and Schedule Ingestion

The **Metadata Agent** extracts dashboards, charts, data models, and other structural metadata from your source and keeps your Collate catalog in sync. It powers discovery, lineage, and governance across your data assets.

When you click **Create & Deploy**, Collate automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the **Agents** tab on the service detail page.

To configure the additional Metadata Agent and schedule ingestion, follow these steps:

1. In the left navigation, click **Connections** and select your service.

2. Click the **Agents** tab.

3. Click **Add Agent** and select **Metadata** from the dropdown.
   <img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/add-metadata-agent.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=accad7d1c4ddf209781bff851d51d464" alt="Add Metadata Agent" width="2398" height="1144" data-path="public/images/ai-2.0/connectors/metadata-ingestion/add-metadata-agent.png" />
   For some services, the dropdown is not available and clicking **Add Agent** takes you directly to the agent configuration page.

4. On the **Configure Ingestion** page, do the following and click **Next**.

   * **Name this Ingestion**: Enter a unique recognizable name for this ingestion pipeline.

     <img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/metadata-agent-name.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=d5ec1f0f3742cadab8cd54c602c97239" alt="Name this Ingestion" width="1578" height="644" data-path="public/images/ai-2.0/connectors/metadata-ingestion/metadata-agent-name.png" />

   * **Agent Setup**: Configure ingestion parameters. The following fields are available:

     | Field                    | Default | Description                                                                                                                                                                                                                                                                                                                                            |
     | ------------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
     | Db Service Prefixes      | —       | List of database service name prefixes used to resolve lineage between dashboards and database assets. Accepted formats: `DBService`, `DBService.Database`, `DBService.Database.Schema`, `DBService.Database.Schema.Table`.                                                                                                                            |
     | Query Parser Type        | Auto    | Select the SQL parser used for lineage extraction from dashboard queries. **Auto** selects the best available parser automatically. **SqlGlot** is a high-performance parser with excellent dialect support; falls back to SqlParse on failure. **SqlFluff** is a comprehensive parser with strong dialect support; falls back to SqlParse on failure. |
     | Mark Deleted Dashboards  | On      | Soft-delete dashboards in Collate when they are removed from the source. Associated lineage is also deleted.                                                                                                                                                                                                                                           |
     | Mark Deleted Data Models | On      | Soft-delete data models in Collate when they are removed from the source. Associated lineage is also deleted.                                                                                                                                                                                                                                          |
     | Mark Deleted Charts      | On      | Soft-delete charts in Collate when they are removed from the source.                                                                                                                                                                                                                                                                                   |
     | Include Data Models      | On      | Ingest data model metadata.                                                                                                                                                                                                                                                                                                                            |
     | Include Draft Dashboards | On      | Ingest dashboards that are in draft state.                                                                                                                                                                                                                                                                                                             |
     | Include Usage            | On      | Collect and ingest usage statistics for dashboards.                                                                                                                                                                                                                                                                                                    |

     <img src="https://mintcdn.com/collatedocs/VsJxWKWlvReeFtlo/public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-agent-setup.png?fit=max&auto=format&n=VsJxWKWlvReeFtlo&q=85&s=4331bedb92cf4fc886548ed7e9d9caf7" alt="Agent Setup" width="1570" height="1434" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-agent-setup.png" />

   * **Filter Patterns**: Apply include or exclude rules to scope which dashboards, charts, data models, and projects this agent ingests. These follow the same filter options described in **Step 5**.

     <img src="https://mintcdn.com/collatedocs/VsJxWKWlvReeFtlo/public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-filter-pattern.png?fit=max&auto=format&n=VsJxWKWlvReeFtlo&q=85&s=fafba3522eb159607f520f8252cace56" alt="Filter Patterns" width="1546" height="844" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-filter-pattern.png" />

   * **Scope & Behaviour**: Control what metadata to include and how to handle deletions. Toggle each option on or off based on your needs:

     | Toggle                 | Default | Description                                                                                                                                                                                           |
     | ---------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
     | Enable Debug Log       | Off     | Sets the ingestion log level to DEBUG. Useful for troubleshooting.                                                                                                                                    |
     | Include Current Owners | Off     | When enabled, replaces the current owner with a new owner from the source if the current owner is null. Recommended to keep enabled during the first metadata ingestion to capture owner information. |
     | Include Tags           | On      | Ingest tags from the source.                                                                                                                                                                          |
     | Override Metadata      | Off     | When on, source values overwrite existing descriptions, tags, owners, and display names in Collate. When off, Collate only updates fields that have no existing value.                                |
     | Override Lineage       | Off     | When on, existing lineage is replaced with newly extracted lineage on each run.                                                                                                                       |

     <img src="https://mintcdn.com/collatedocs/VsJxWKWlvReeFtlo/public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-scope-bahaviour.png?fit=max&auto=format&n=VsJxWKWlvReeFtlo&q=85&s=b62494bc009ab02b79062e74519e89de" alt="Scope & Behaviour" width="1552" height="1014" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-scope-bahaviour.png" />

5. On the **Schedule Interval** page, set when the agent runs:

   * **Schedule**: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression.
   * **On-Demand**: No automatic schedule; trigger the agent manually when needed.

   <img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/schedule.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=25cc1d78f6f2a8bd115830d034d1d8d1" alt="Schedule Interval" width="1588" height="1044" data-path="public/images/ai-2.0/connectors/metadata-ingestion/schedule.png" />

6. Click **Add** to deploy the agent.

## Lineage

Lineage in Collate shows you which database tables power each dashboard. When lineage is set up, you can trace any dashboard back to the exact source tables in your database.

There is no separate lineage agent or lineage pipeline — lineage is collected as part of the same metadata ingestion workflow. To enable lineage, open the **Configure Metadata Agent** section above, scroll to the **Lineage Information** section in the agent setup, and enter one or more database service names in the **Db Service Prefixes** field.

<img src="https://mintcdn.com/collatedocs/VsJxWKWlvReeFtlo/public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-lineage.png?fit=max&auto=format&n=VsJxWKWlvReeFtlo&q=85&s=f5bd7e6138bba796d865fc4ad94697ae" alt="Lineage Information" width="2060" height="1284" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Dashboard/dashboard-lineage.png" />

Configuring **Db Service Prefixes** is optional but recommended — it restricts table matching to specific database services. If left blank, Collate attempts to match source tables across all ingested database services.

| What you enter                  | What it matches                                           |
| ------------------------------- | --------------------------------------------------------- |
| `SnowflakeProd`                 | All tables in the Snowflake service named `SnowflakeProd` |
| `SnowflakeProd.sales_db`        | Tables in the `sales_db` database within `SnowflakeProd`  |
| `SnowflakeProd.sales_db.public` | Tables in the `public` schema within `sales_db`           |

<Tip>
  **Tip**: If your dashboards pull data from multiple database services, add each service as a separate entry in the **Db Service Prefixes** field.
</Tip>

## Securing Tableau Connection with SSL in Collate

To establish secure connections between Collate and Tableau, navigate to the `Advanced Config` section. Here, you can provide the CA certificate used for SSL validation by specifying the `caCertificate`. Alternatively, if both client and server require mutual authentication, you'll need to use all three parameters: `ssl key`, `ssl cert`, and `caCertificate`. In this case, `ssl_cert` is used for the client’s SSL certificate, `ssl_key` for the private key associated with the SSL certificate, and `caCertificate` for the CA certificate to validate the server’s certificate.

<img src="https://mintcdn.com/collatedocs/qybQN_VCNOUNg9nn/public/images/connectors/ssl_tableau.png?fit=max&auto=format&n=qybQN_VCNOUNg9nn&q=85&s=0070f92d483e86d8caeac743f79a92a6" alt="SSL Configuration" height="450px" data-path="public/images/connectors/ssl_tableau.png" />

## Troubleshooting

<Columns cols={2}>
  <Card title="Tableau Troubleshooting" href="/ai-2-0/connectors/dashboard/tableau/troubleshooting">
    Learn more about how to troubleshoot common Tableau connector issues and resolve configuration or ingestion errors.
  </Card>
</Columns>

## Reverse Metadata

* **Description Management**: Tableau supports description updates at the following levels:
  * Dashboard level
  * Chart level

* **Owner Management**: Tableau supports owner management at the following levels:

  * Dashboard level

  Owner management is not supported for Charts as ownership in Tableau is managed at the workbook level.

* **Tag Management**: Tableau supports tag management at the following levels:
  * Dashboard level
  * Chart level

For more information about reverse metadata ingestion, see [Reverse Metadata Application](/ai-2-0/admin-guide/applications/reverse-metadata).