Skip to main content

Capabilities

The Tableau connector supports automatic account provisioning and deprovisioning. Notes:
  • Workbooks in a user’s Personal Space don’t belong to a project, so C1 doesn’t sync them or their views.
  • C1 syncs membership of the built-in All Users group but can’t change it, because Tableau doesn’t allow that group to be modified through the API.
  • C1 doesn’t show users with the Server Administrator site role as group members.

Licenses and seats

In Tableau, licensing is role-based: each user’s site role determines their license tier. There is no separate license object to assign — granting a license means setting the user’s site role. The connector surfaces four tiers:
  • Creator — full authoring, data preparation, and publishing
  • Explorer — browse, interact, and publish with existing data sources
  • Viewer — view and interact with published dashboards
  • Unlicensed — no access to site features
When your Tableau site has per-tier seat capacities configured, C1 tracks the purchased and consumed seat counts for each license tier, so you can review license utilization alongside who holds each tier.
Because a tier is a view of the user’s single site role, several roles can satisfy one tier (for example, a Site Administrator Creator counts as Creator), and the four tiers are mutually exclusive in C1 with no default tier or ranking. Granting a tier the user already holds changes nothing and keeps their current role. Administrators are refused when you grant them a different tier: change their role through the Site Role entitlement instead. For any other user, granting a tier sets their site role to that tier’s base role, and C1 replaces their previous tier grant when the previous role belonged to a recognized tier. Granting to a user that no longer exists returns a not-found error. Revoking a tier a user still holds sets them to Unlicensed, including users with an administrator role. Revoking from a user who no longer exists, or who no longer holds the tier, changes nothing; the same applies to revoking Unlicensed from an Unlicensed user, and the next sync still shows that user as Unlicensed. To give a revoked administrator their role back, assign it through the Site Role entitlement. Server Administrator exists only on Tableau Server and this connector cannot assign it, so a revoked Server Administrator stays Unlicensed until a server administrator restores the role in Tableau. Revoke also fails if the user belongs to a group with a “Grant role on sign in” minimum site role; remove them from that group first.
Revoking a license fails if the user belongs to a group with a Grant role on sign in minimum site role. Tableau returns Site role of link user that belongs to license upon login cannot be lower than minimum site role of group. Remove the user from that group first, then revoke the license.

Permission inheritance

Tableau uses a permission inheritance model that affects how access is synced and provisioned:
  • Projects with LockedToProject: When a project’s content permissions are set to LockedToProject, workbooks inside that project inherit the project’s permissions and cannot be granted or revoked independently — permissions must be changed at the project level instead.
  • Workbooks with showTabs=true: Views (dashboards) inside these workbooks inherit their permissions from the workbook. View-level permissions cannot be granted or revoked independently — attempting to do so returns a clear error. Use the workbook entitlement instead.
  • Workbooks with showTabs=false: Views have their own independent permission assignments, which can be granted and revoked directly.
  • Permissions granted to a group: Every member of the group holds the permission, and C1 shows the group as the source of each member’s grant.
If a locked project’s name contains a comma (,) or an ampersand (&), C1 doesn’t sync the access its workbooks inherit from that project, because Tableau rejects these characters in the filter the connector uses to find them. Rename those projects without commas or ampersands to sync their inherited access.
Revoking a permission from a user who holds it only through a group doesn’t remove their access: the next sync shows it again, granted through the group. Revoke the permission from the group, or remove the user from the group.

Gather Tableau credentials

Configuring the connector requires you to pass in credentials generated in Tableau. Gather these credentials before you move on.
A user with the Server Administrator role in Tableau Server or Site Administrator in Tableau Cloud must perform this task.
To work with the Tableau APIs, you’ll need either an installation of Tableau Server or membership in the Tableau Developer Program, which grants you a personal Tableau Cloud sandbox.

Generate a Personal Access Token

1
Sign into Tableau Server or Tableau Cloud.
2
In the menu bar at the top of the page, click your profile image or initials and select My Account Settings from the menu.
3
In the Personal Access Tokens area of the page, enter a name for your new token (such as “C1 integration”) and then click Create.
4
Carefully copy and save the newly generated token and its name.

Locate your server path and site ID

1
Locate your server path, which is the base URL for your Tableau server.
2
Locate your site ID, which is the value that appears after /site/ in the full URL for your Tableau instance.Examples:For a Tableau Server instance with the URL http://SampleServer#/site/SecurityTeam/projects, the server path is SampleServer and the site ID is SecurityTeam.For a Tableau Cloud instance with the URL https://10ay.online.tableau.com#/site/MarketingTeam/workbooks, the server path is 10ay.online.tableau.com and the site ID is MarketingTeam.Done. Next, move on to the connector configuration instructions.

Configure the Tableau connector

To complete this task, you’ll need:
  • The Connector Administrator or Super Administrator role in C1
  • Access to the set of Tableau credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Tableau and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter the site ID and server path into the Site ID and Server path fields.
9
Enter the name of the personal access token into the Access token name field.
10
Enter the personal access token value into the Access token secret field.
11
Click Save.
12
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Tableau connector is now pulling access data into C1.

Configure IDP-based account provisioning

When provisioning Tableau accounts (Licenses resource type), the connector supports two optional fields in the provisioning mapping that control how new accounts are authenticated: These fields appear in the provisioning mapping for the Licenses entitlement in C1 and are not part of the connector’s base configuration.

Behavior reference

If your Tableau Server uses an API version older than 3.22 and you do not set IDP Configuration Name, account provisioning uses the site default authentication without error. The IDP endpoint is only required when you explicitly configure an IDP name.