# SailPoint Claude Enterprise Connector Documentation > Claude Enterprise Connector Documentation # Documentation # Connecting SailPoint and Claude Enterprise To connect SailPoint with Claude, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Select **Create Manual Work Items** to allow the connector to create manual work items for certain operations. You can also enable this option so the source supports additional source management features such as creating accounts and access profile management. > **Important** > > Once you enable this feature, you cannot disable it. For more information on manual work items in SailPoint, refer to [Work Items](). For more information on SailPoint features, refer to [SailPoint Identity Services](). 7. Select **Save**. ## Connection Settings The following settings control how SailPoint connects to Claude. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() - **API Base URL** - Claude API endpoint the connector uses. Do not change the base URL; it must be [https://api.anthropic.com](). - **Compliance API Key** - Enter the Compliance API key to allow the connector to authenticate and access compliance data for your Claude Enterprise organization. ## Aggregation and Advanced Settings ### Aggregation Settings > [!NOTE] > > **Screenshot** > > [![Aggregation settings organizations dropdown]()]() - **Organizations** - Select one or more organizations to include in aggregation. If no organizations are selected, data from all organizations is included. > [!NOTE] > > Save a valid **Compliance API key** on **Connection Settings** first, then use **Test Connection** or refresh to load the organization list. ### Advanced Settings > [!NOTE] > > **Screenshot** > > [![Advanced settings connection timeout and page size]()]() - **Connection Timeout (in Minutes)** - Enter the number of minutes a connection times out after inactivity. Default is 1 minute. - **Page Size** - Enter the number of records to retrieve per page, between 1 and 1,000. Default is 100. ## Machine Identity Governance Settings In SailPoint, the page heading may display as **Claude Agent Governance Settings**. > [!NOTE] > > **Screenshot** > > [![Machine Identity Governance Settings]()]() Use this page to configure Claude Managed Agent aggregation for one or more workspaces. 1. Select **Enable Claude Managed Agents** to turn on managed agent aggregation. 2. **Include Archived Managed Agents** is enabled by default after you enable **Enable Claude Managed Agents**. Clear this toggle if you do not want to aggregate archived agents. For details on the agent lifecycle in Claude, including archiving, refer to [Agent lifecycle]() in the Claude documentation. 3. Use multi-workspace support to aggregate managed agents across workspaces. 1. Enter the **Workspace Identifier** as the organization name and workspace name so agents from different workspaces are represented correctly. Use the format `OrgName:WorkspaceName`. 2. Enter the **Workspace API key** to authenticate and access Claude platform agent data. 3. Select **Add** to include another workspace row, and then enter the next **Workspace Identifier** and **Workspace API key**. 4. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Integrating SailPoint with Claude Enterprise SailPoint's Claude Enterprise connector supports access governance for Anthropic Claude Enterprise users, compliance roles, compliance groups, and [Claude Managed Agents](). This integration helps you enforce policy-based access controls so that only the appropriate users can access critical AI Agents. It enables you to manage users, compliance, and AI agents across your organization. You can use this documentation for the requirements and field definitions that you need to configure the Claude Enterprise connector. To manage account data, create an identity profile based on the source, or verify that the loaded accounts correlate to an existing identity. To connect to Claude, refer to [Connecting SailPoint and Claude](). For Claude Managed Agents and machine identity settings, refer to [Machine Identity Governance Settings](). > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Claude Enterprise source supports the following features: - **Account Aggregation** - All organization users as accounts. - **Entitlement Aggregation** - Organization roles (`organizationRole`), compliance roles (`complianceRole`), and compliance groups as entitlements. - **Privilege Classification** - Recommended privilege levels for organization roles. For the role-to-level mapping, refer to [Entitlement Attributes](). - **Machine Identity Aggregation** - Managed Agents from beta APIs into Agent Identity Security. > [!NOTE] > > To aggregate agents, SailPoint is using beta API endpoints that are subject to change. SailPoint is aligned with Anthropic to manage future changes. > [!NOTE] > > Datasets are also available in SailPoint Agentic Fabric. Contact your Customer Success team and refer to [SailPoint Agentic Fabric]() for more information. ### Non-Human Identity Discovery - Aggregate Claude Managed Agents Refer to [Machine Identity Governance Settings]() for more information. Refer to [Discovering Potential Non-Human Accounts]() for more information. ## Prerequisites The following prerequisites are required: - You must be a Primary Owner on a Claude Enterprise plan. - Compliance API must be enabled. - A compliance API Key created. > [!NOTE] > > Claude Enterprise plans generally include Compliance API, except for Public Sector organizations. To enable the Compliance API and create a compliance API key: 1. Select **Organization settings \> Data and privacy**. 2. In the Compliance API section, select **Enable**. 3. Select + **Create key** to create compliance access keys. 4. Provide the following scopes: - `read:compliance_org_data` - `read:compliance_user_data` - `read:compliance_activities` To create a Workspace API key: 1. Select **Organization settings \> API Keys**. 2. Create a new API key by selecting **\+ Create key**. 3. Record the organization name and workspace name. They are required for the workspace identifier. > [!NOTE] > > API keys are owned by workspaces and remain active even after the creator is removed. # Machine Identity Schema Attributes Machine Identity attributes define the multiple types of machine identities that can be assigned to the managed system's user accounts. For more information, refer to [Machine Identity Security Overview](). The following lists the Claude Managed Agent attributes. | Attribute Name | Description | | --- | --- | | identity | The unique machine identity ID SailPoint assigns, using sanitized organization and workspace from the workspace identifier, Anthropic agent ID, and version. | | id | The Anthropic agent ID shared across versions (for example, `agent_*`). | | agentName | The display label SailPoint assigns for that identity; uses the agent name where the ID uses raw agent identifiers. | | created\_at | Shows when Claude created this agent version (ISO 8601). | | archived\_at | Shows when Claude archived this version, if applicable; empty if this is the active version. | | spStatus | Claude agent status derived from `archived_at`: `Active` when the version is not archived and `Inactive` when Claude provides an archive timestamp. | | description | The description administrators set for this agent version in Claude. | | mcp\_servers | JSON string of MCP server configurations; `[]` if none. Also listed under resources with kind `mcp_server`. | | metadata | JSON string of optional vendor metadata for this version. | | model\_id | The configured Claude model (for example, `claude-sonnet-4-6`). | | model\_speed | The inference tier, such as standard or fast. | | name | The display label SailPoint assigns for that identity (colon-delimited composite: organization and workspace from workspace identifier `OrgName:WorkspaceName`, agent display name, version). | | skills | JSON string of skill bundles linked to this version; `[]` if none. | | system | The default system instructions for this agent version. | | tools | JSON string of tool definitions for this version; `[]` if none. | | type | The resource type from Claude; always `agent` for these records. | | updated\_at | Shows when Claude last updated this agent version (ISO 8601). | | version | The published version number for this agent configuration. | # Schema Reference The application schema is used to configure the objects returned from a connector. > [!NOTE] > > - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Claude Enterprise connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the Claude Enterprise source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | email | Equals | Work Email | ## Default Account Schema Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location. The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas]() for more information. ### Default Account ID SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*. > [!CAUTION] > > Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts. > > To resolve issues caused by changing account IDs, reconfigure them to their default values. The following table lists the default account IDs for this connector: | Account ID | Schema Object Type | | --- | --- | | id | Account | | id | Compliance Groups | | id | Organization Roles | | identity | Compliance Roles | | identity | Agents | > [!NOTE] > > For organizational users, the account native identifier is `id`. SailPoint uses this value as-is for account correlation. The account schema does not use `identity`. > [!NOTE] > > For Claude Managed Agents, the identity attribute (native identifier) uses `:::`. ### Default Account Attributes The Claude Enterprise connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. | Attribute Name | Description | | --- | --- | | id | The native user identifier in Claude Enterprise. SailPoint uses this value as the account native identifier for correlation. | | email | The email address for this user in Claude Enterprise. | | full\_name | The display name SailPoint shows for this account. Account display names use this value only and do not include the organization name. | | created\_at | Shows when the user joined the organization (RFC 3339 from the Claude API). | | last\_login | The user's last successful authentication date and time. | | last\_login\_method | The user's last successful authentication method. | | organization\_uuids | The Claude Enterprise organization IDs associated with this account. | | organization\_names | The display names of the Claude Enterprise organizations associated with this account. | | organization\_roles | The organization-scoped roles for this user across selected organizations. Values use the `organization_uuid:organization_role` format and match `organizationRole` entitlement identities. | | groups | The compliance groups this user belongs to; values are group IDs that match group entitlements from this source. | > [!NOTE] > > To read `last_login` and `last_login_method`, include the `read:compliance_activities` scope in your Compliance API key. These fields are not included by default; add them only when required because they are resource-intensive and can increase aggregation time. ## Default Entitlement Attributes Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements]() for more information. > [!CAUTION] > > Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations. **Organization Roles (`organizationRole`)** | Attribute Name | Description | | --- | --- | | id | The organization-scoped role key in SailPoint format: `organization_uuid:organization_role`. | | role\_name | The organization-scoped display label shown in SailPoint: `organization_name:organization_role`. | | organization\_role | The native organization role value from Claude Enterprise, such as `org_admin` or `member`. | | organization\_uuid | The Claude Enterprise organization ID that owns this organization role entitlement. | | organization\_name | The Claude Enterprise organization name that owns this organization role entitlement. | SailPoint Privilege Classification recommends privilege levels for `organizationRole` entitlements based on the native `organization_role` value. | Privilege Level | Organization Role | Description | | --- | --- | --- | | High | `admin` | Administrative user who can manage organization settings, users, and access depending on the organization configuration. | | High | `billing` | User with access to billing, invoices, payments, and financial administration. | | High | `membership_admin` | User responsible for managing organization members, invitations, and membership-related settings. | | High | `primary_owner` | Main owner of the Claude organization with the highest administrative control and account ownership. | | High | `owner` | Organization owner with broad permissions to manage organization settings, users, and access. | | Medium | `developer` | User with access to developer and API-related features such as API keys, projects, or platform usage. | | Medium | `managed` | Organization-managed user, often controlled through enterprise identity, SSO, or SCIM. | | Low | `claude_code_user` | User assigned access to Claude Code features. | | Low | `user` | Regular organization member with standard Claude access and no elevated admin or billing privileges. | For more information, refer to [Managing Privilege Classification](). **Compliance Roles (`complianceRole`)** | Attribute Name | Description | | --- | --- | | roleName | The display name SailPoint shows for this role, using the organization label and the role name. | | id | The Anthropic role id (for example, rbac\_role\_\*). | | identity | The unique role id SailPoint uses for correlation: sanitized owning organization UUID and Anthropic role id, joined with :. | | name | The role title in Claude Enterprise. | | description | The role description from Claude Enterprise, if provided. | | created\_at | When the role was created (ISO 8601 from Claude). | | updated\_at | When the role was last updated (ISO 8601 from Claude). | | organization\_uuid | The organization id on this entitlement for reporting; set from your connector org scope. | **Compliance Groups** | Attribute Name | Description | | --- | --- | | id | The Anthropic group ID (for example, rbac\_group\_\*). | | name | The group name in Claude Enterprise. | | description | The group description from Claude Enterprise, if provided. | | source\_type | Shows whether Claude created the group directly or SCIM provisioned it. | | created\_at | Shows when Claude created the group (ISO 8601). | | updated\_at | Shows when Claude last updated the group (ISO 8601). | | organization\_uuid | The organization ID on this entitlement for reporting; set from your connector organization scope. | | roles | The compliance roles attached to this group; values are identities that match complianceRole entitlements from this source. | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](). ## Workspace key not visible after moving to Multi-Workspace **Issue**: Workspace keys are not visible after you move from a single-workspace setup to multi-workspace support. Workspace keys from the single-workspace setup are not migrated automatically. **Resolution**: Re-add all required workspace key(s) in the Multi-Workspace table on [Machine Identity Governance Settings](). Agent aggregation runs only for the workspace key(s) listed in the Multi-Workspace table.