# SailPoint Attio Connector Documentation

> Attio Connector Documentation

# Documentation

# Connecting SailPoint and Attio

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring 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. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **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](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

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**
   >
   > Source name must be unique.
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](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
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.

### Standard Setup

Configure more detailed settings relative to Express Setup.

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](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
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](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## 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 descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Attio API host as **Base URL**. Do not add `/v2` or a trailing slash. Use `https://api.attio.com`.
2. Enter the workspace access token as **API Token**. SailPoint sends the token as a Bearer token.
3. Select **Save**.

> [!NOTE]
>
> Use a **workspace API key**, not a person's Attio login password. Do not complete an OAuth app flow for this source.

## 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](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Attio

Attio is a cloud CRM that manages **workspace members** and their **access level** in a workspace. The Attio connector is a **read-only** connector. It provides limited governance for your Attio system: user aggregation and role (access level) visibility for Quick Compliance. This document provides the instructions required to configure a new direct connection between SailPoint and Attio. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Attio connector supports the following:

### Account Management

- Aggregate Workspace members

### Entitlement Management

- Aggregate Access level - role in the Attio workspace: admin, member, or suspended

> [!NOTE]
>
> This connector is read-only. It supports account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported in this release. Access level values are collected during account aggregation.

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## Key Implementation Notes

- Each member has **one** access level.
- Attio does **not** delete workspace members. Suspended people still appear as accounts, with access level `suspended`.
- SailPoint correlates the Attio account to an identity using **email**.
- One SailPoint source = one Attio workspace (the workspace that issued the API token).
- There is no separate catalog of roles in Attio. Access level is read from each member and shown as an entitlement on the account.

## Prerequisites

Before configuring the Attio connector, ensure the following requirements are met:

1. Sign in at an [Attio workspace](<https://app.attio.com/>).
2. An **admin** in that workspace. Only admins can create API keys.
3. A workspace **access token** (API key) with permission to view workspace members.
4. You have a Base URL.

### Create the API Token

1. Sign in to Attio as a workspace **admin**.
2. Select the dropdown beside your workspace name and select **Workspace settings**.
3. Select the **Developers** tab.
4. Select **New access token**.
5. Add a token name (for example, `SailPoint`).
6. Set scopes so the token can **view workspace members**. Include `user_management:read`. You do not need write scopes for this connector.
7. Copy the token and store it securely. You will paste it into the SailPoint **API Token** field.

> [!NOTE]
>
> Treat the token like a password. If you delete or replace the token in Attio, update the source in SailPoint. Tokens do not expire until an admin deletes them.

## Required Permissions

| Who | Access |
| --- | --- |
| **Attio workspace admin** | Can create and manage API tokens in **Workspace settings \> Developers** |
| **API token with user\_management:read** | Recommended. Can list workspace members for aggregation |
| **API token without user-management scope** | Test Connection and account aggregation fail |
| **Non-admin Attio user** | Cannot create the API token |

You only need **read** access. This connector does not write to Attio.

For more detailed information on Attio API authentication, refer to the following resources:

- [Attio website](<https://attio.com/>)
- [Generating an API Key](<https://attio.com/help/apps/other-apps/generating-an-api-key>)
- [Attio API Authentication](<https://docs.attio.com/rest-api/guides/authentication>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

# 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](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Attio connector uses the following default correlation and object configurations.

## 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](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) 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(User) |

### Default Account Attributes

The Attio 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 | Unique identifier of the workspace membership |
| firstName | Member's given name |
| lastName | Member's family name |
| email | Member's login email |
| accessLevel | Role in the Attio workspace (managed entitlement) |
| createdAt | When this workspace membership was created |

> [!NOTE]
>
> Access level is modeled as an account entitlement on the `accessLevel` attribute. A separate entitlement schema is not used. Access level values are `admin`, `member`, and `suspended`.