After Installing the Connector you can connect and create a Data Source for data in Claude Compliance.

Setting Up a Data Source

Complete the following steps to connect to the data:

1. Under Connect | To a Server, click More....
2. Select the data source called Claude Compliance by CData.
3. Enter the information required for the connection.
4. Click Sign In.
5. If necessary, select a Database and Schema to discover what tables and views are available.

Using the Connection Builder

The connector makes the most common connection properties available directly in Tableau. However, it can be difficult to use if you need to use more advanced settings or need to troubleshoot connection issues. The connector includes a separate connection builder that allows you to create and test connections outside of Tableau.

There are two ways to access the connection builder:

• On Windows, use a shortcut called Connection Builder in the Start menu, under the CData Tableau Connector for Claude Compliance folder.
• You can also start the connection builder by going to the driver install directory and running the .jar file in the lib directory.

In the connection builder, you can set values for connection properties and click Test Connection to validate that they work. You can also use the Copy to Clipboard button to save the connection string. This connection string can be given to the Connection String option included in the connector connection window in Tableau.

Connecting to Claude Compliance

The connector connects to Claude Compliance using a Compliance Access Key. This is the only supported authentication method.

Authenticate with a Compliance Access Key

To create a Compliance Access Key:

1. Enable the Compliance API for your organization.
2. Sign in to claude.ai as a primary owner or organization owner and open Organization settings > API > Keys.
3. Select Create Key and assign only the scopes your integration needs:
   • read:compliance_activities for Activities and the typed activity views.
   • read:compliance_org_data for organizations, roles, groups, and settings.
   • read:compliance_user_data for users, chats, files, projects, and downloads.
   • delete:compliance_user_data for the explicit Delete* stored procedures.
4. Create the key.
5. Copy the key when it appears. The key starts with sk-ant-api01- and is shown only once.

Then set the following connection property:

• APIKey: The Compliance Access Key you created.

Optional connection properties

The OrganizationUUID parameter determines which organization is used in organization-scoped views (such as OrganizationUsers, ComplianceRoles, and ComplianceRolesPermissions). When set, these views are limited to a single linked organization.

If OrganizationUUID is left empty, the view defaults to the first available organization but does not include data from all linked Organizations.

Next Step

See Using the Connector to create data visualizations.