Skip to content
Merulan

Tableau setup

What an operator supplies to connect the Tableau Source, and the verification the provider requires.

Connecting Tableau accepts a named secret bundle the operator fills in. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Tableau refuses the connection until every item holds.

  • A Tableau site, and an administrator who may create a connected application.
  • A provisioned technical user the connected application signs in as.
  • An administrator available for rotation, because Tableau rotates the connected-app secret rather than Merulan.

Credentials

Tableau stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • A client identifier, a secret identifier, the secret itself, and the technical-user subject, supplied together as one connected-app bundle. No personal access token and no password are accepted.

Scopes

Tableau carries no scope list in Merulan: the technical user the connected application signs in as holds the requested scopes for this Source.

Tableau carries no scope list here. Reach is the permission set on that user, so narrow the user rather than a scope list.

Verification

Workspace-issued credential governs the Tableau connection. The customer creates the connected application on their own site, so the site administrator holds the whole admission decision.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.