Enabling SSIS in Visual Studio 2022

If you're using Visual Studio 2022, you will need to install the SQL Server Integration Services Projects extension to use SSIS.

1. Navigate to Extensions > Manage Extensions.
2. In the Manage Extensions window's search box, search for "SQL Server Integration Services Projects 2022" and select the extension in the list.
3. Click Download.
4. Close Visual Studio and run the downloaded Microsoft.DataTools.IntegrationServices.exe installer. Proceed through the installer with default settings.
5. Open Visual Studio. There should now be an "Integration Services Project" project template available.

Adding the Claude Compliance Connection Manager

Create a new connection manager as follows:

1. Create a Visual Studio project with the "Integration Services Project" template.
2. In the project, right-click within the Connection Managers window and select New Connection from the menu.
3. In the Description column, select CData Claude Compliance Connection Manager and click Add...
4. Configure the component as described in the next section.

Alternatively, if you have an existing project and CData Claude Compliance Source or CData Claude Compliance Destination:

1. Right-click your CData Claude Compliance source or destination component in your data flow
2. Select Edit... to open an editor window.
3. Click the New... button next to the Connection manager: dropdown selector to create a connection manager.
4. Configure the component as described in the next section.

Connecting to Claude Compliance

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