Skip to content

Tableau Connections

Tableau connections are saved connection profiles that Antares can use for environment analysis, workbook inventory, and optional usage data.

If you are creating your first Tableau connection, start with Connect Tableau. This page is the detailed reference for authentication, permissions, usage data, statuses, and connection management.

Each Tableau connection includes:

  • Connection name and optional description.
  • Server URL.
  • Site ID or Tableau Server default site setting.
  • Installation type: Tableau Cloud or Tableau Server.
  • Authentication method: Personal Access Token or JWT Connected App.
  • Optional usage data configuration.
  • Last connection test status and last tested time.

Secrets are stored as credentials. The Connections list shows the connection metadata and status, not the secret values.

Antares supports both Tableau Cloud and Tableau Server through Tableau APIs.

Tableau Cloud: enter the Tableau Cloud URL and the Site ID. For example, if the URL contains /site/mycompany/, use mycompany.

Tableau Server: choose Default Site when the Tableau Server URL has no /site/ segment. Choose Custom Site when the URL includes /site/your-site-id.

Connection tests run from the Antares environment. If Antares cannot reach Tableau over the network, the connection will fail even when the same Tableau URL works for you locally.

Tableau environmentWhat Antares must reach
Tableau CloudThe Tableau Cloud site URL over HTTPS.
Tableau ServerThe Tableau Server API endpoint from the network where Antares runs.
Tableau Server usage dataThe Tableau Server PostgreSQL repository host and port when repository access is enabled.

If Tableau Server is only available inside your private network, Antares may need a private-network deployment path. See Private Network Access for rollout planning guidance.

Antares supports two Tableau authentication methods.

MethodRequired valuesNotes
Personal Access TokenToken Name, Token SecretThe Token Secret is shown once when the token is created.
JWT (Connected App)Client ID, Secret ID, Secret Value, UsernameOnly Direct Trust connected apps are supported.

Use Personal Access Token authentication when the connecting Tableau user has a token for Antares.

In Tableau, create a token from the user account settings, then copy the Token Name and Token Secret into Antares.

Use JWT authentication when your Tableau site uses a Direct Trust connected app.

The connected app must provide:

  • Client ID.
  • Secret ID.
  • Secret Value.
  • Username for the Tableau user Antares should authenticate as.

For Tableau Cloud, the username must be in email format. For Tableau Server, the username format depends on the server configuration.

The connecting Tableau user controls what Antares can see. Results are limited to the workbooks, projects, users, groups, and usage sources visible to that identity.

AccessRequiredAffects
List workbooks and projectsYesEnvironment inventory and workbook selection.
Download workbooksYesWorkbook structure analysis and migration scoring.
List users and groupsOptionalOwnership, user, and group context in reports.
Usage statisticsOptionalUsage trends, workbook activity, and migration prioritization.

Site Administrator access is recommended when you need full workbook inventory, user and group details, and usage statistics.

Usage data is optional. It helps Antares show workbook views, user activity, and content engagement.

For Tableau Cloud, Antares can collect usage data from Admin Insights using the TS Events datasource.

Usage data collection uses the same Tableau connection and credentials. No repository database credentials are required.

By default, Admin Insights is available to Site Administrators. A Site Administrator can also grant access to the Admin Insights project for other users.

For Tableau Server, Antares can collect usage data from the Tableau Server PostgreSQL repository.

Enable repository access in the Usage Data step and provide the repository database credentials.

HostTableau Server repository host.
Port8060 by default.
Databaseworkgroup by default.
Usernamereadonly by default.
SSL Modedisable or require.

Use a read-only repository database user with the minimum access required to read usage tables.

Run Test Connection to verify that Antares can authenticate with Tableau and reach the selected site.

A successful connection test can show server version, API version, site name, and authenticated user.

The Connections list shows connection status:

ConnectedThe most recent connection test succeeded.
FailedThe most recent connection test failed.
Not configuredThe connection has not been successfully tested yet.

Usage data has its own status:

StatusMeaning
Not configuredUsage data was not enabled for the connection.
Not testedUsage data was enabled but has not been tested.
VerifiedUsage data access was tested successfully.
Not availableThe usage source is not available for the connection.
Limited accessAntares reached part of the usage source, but one or more checks failed.

If a connection includes usage data, testing the connection from the Connections list also checks the configured usage source.

Open Connections and select the Tableau tab to manage saved Tableau connections.

The list shows:

  • Name and description.
  • Server URL.
  • Site ID or Default Site.
  • Type: Cloud or Server.
  • Usage data source and status.
  • Authentication method.
  • Connection status.
  • Last tested time.

You can retest or delete a connection from the Actions column.

Deleting a connection removes the saved connection profile and credentials. Existing analyses keep their generated results, but new analyses cannot use the deleted connection.

Connection tests verify saved credentials and reachability. Analysis pre-checks run when you create an analysis from a Tableau connection.

The analysis pre-check validates the capabilities needed for that analysis, including workbook visibility, project visibility, optional user and group access, and optional usage data availability.