ODBC Driver for Claude Compliance

Build 26.0.9770

Windows DSN Configuration

Using the Microsoft ODBC Data Source Administrator

You can use the Microsoft ODBC Data Source Administrator to edit the DSN configuration. Note that the DSN is created during the installation process.

Complete the following steps to edit the DSN configuration:

  1. Select Start > Search, and enter ODBC Data Sources in the Search box.
  2. Choose the version of the ODBC Administrator that corresponds to the bitness of your application (32-bit or 64-bit).
  3. Click the System DSN tab.
  4. Select the system data source and click Configure.
  5. Edit the information on the Connection tab and click OK.

Note: For .NET Framework 4.0, the driver distributes Microsoft Visual C++ 2015-2022 Redistributable. For .NET Framework 3.5, the driver distributes Microsoft Visual C++ 2008 Redistributable.

Ensuring Registry Access

The driver stores connection information in the Windows registry. To ensure that the driver can write to the registry, perform either of the following actions:

  1. Run the calling application as an administrator.
  2. Connect via a User DSN instead of a System DSN.

Connecting to Claude Compliance

The driver 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.

Copyright (c) 2026 CData Software, Inc. - All rights reserved.
Build 26.0.9770