# SailPoint Cobot Connector Documentation

> Cobot Connector Documentation

# Documentation

# Connecting SailPoint and Cobot

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 Cobot API base URL as **Base URL**. For example, `https://api.cobot.me`.
2. Enter the **API Token**.
3. Select **Save**.

> [!NOTE]
>
> SailPoint recommends using HTTPS for a secured connection. SailPoint uses the Base URL and API Token together to authenticate all requests to Cobot - no additional headers need to be configured manually.

## 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 Cobot

Cobot is coworking space management software that helps operators run shared office spaces - handling memberships, plans, bookings, invoicing, and teams of members. This document provides instructions to configure a new direct connection to a Cobot source. 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 Cobot connector supports the following:

### Account Management

- Aggregate Users

### Entitlement Management

- Aggregate Teams

> [!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.

## Prerequisites

Ensure the following prerequisites are met before proceeding with the configuration:

1. You have access to your Cobot account and can register applications.
2. You know your Cobot API base URL.
3. You have registered an OAuth2 client application and stored its generated Access Token, used as the connector's API Token.

### Create an API Token

1. Sign in to your Cobot account.
2. Go to the [Cobot developer portal](<https://dev.cobot.me/>).
3. Select the **OAuth Clients** tab, then select **Register your application** (or open an existing registration, for example, SailPoint Cobot Connector).
4. When registering the application, set the **Scope** to the permissions the connector needs (for example, `read_memberships`, `read_spaces`, `read_teams`, `read_user`) and supply a **Redirect URL** - OAuth2 client registration requires one, even though the connector does not use the interactive OAuth2 flow.
5. After the application is registered, Cobot automatically generates an Access Token for it on the same page, tied to the registering user. Copy and save this Access Token - this is the value used as the connector's API Token.

> [!NOTE]
>
> This Access Token does not expire on its own; Cobot issues it once, at the time the OAuth2 client application is registered, rather than through a separate token-request step. It is scoped to the user who registered the application and is intended mainly for testing and non-interactive apps such as this connector. Do not confuse it with the application's Client Secret, which is used only for the interactive OAuth2 authorization-code flow.

## Required Permissions

Cobot uses a centralized API base domain. The token inherits the OAuth2 scope granted when the client application was registered. To manage space members and teams, register the application with the following scope:

- `read_user` - Access to the authenticated user's profile
- `read_memberships` - Access to space memberships (id, name, email, phone, company, confirmedAt, canceledAt, photo, space\_id, team)
- `read_teams` - Access to teams within the space (team\_id, team\_name, customerNumber, billingCompany, billingEmails, space\_id), used to model entitlements
- `read_spaces` - Access to the space associated with the memberships and teams

> [!NOTE]
>
> This connector is Read Only - the registered scope only needs to cover the `read_*` permissions above. If you scope the application more narrowly, the connector will only be able to read the data covered by the granted scope.

## Support

For any help with the Cobot API, refer to the [Cobot API documentation](<https://dev.cobot.me/>).

> [!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 Cobot 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 |

### Default Account Attributes

The Cobot 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 membership account |
| name | Full name of member |
| email | Email address of the member |
| phone | Phone number of member |
| company | Company associated with the member |
| confirmedAt | Membership confirmation date |
| canceledAt | Membership cancellation date, if any |
| photo | URL of the members profile photo |
| space\_id | Identifier of the space associated with the membership |
| team\_id | Identifier of the team assigned to the member |

> [!NOTE]
>
> `team_id` is of type team and is flagged as an Entitlement attribute - it links each account to the Team entitlement schema below.

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

### Default Team Attributes

| Attribute Name | Description |
| --- | --- |
| team\_id | Unique identifier of the team |
| team\_name | Team name |
| customerNumber | Customer number associated with the team |
| billingCompany | Company name in the billing address |
| billingEmails | Billing email address of the team |
| space\_id | Identifier of the space associated with the team |

> [!NOTE]
>
> Cobot teams are flat - a space can have multiple teams, but teams do not nest inside one another. Each team is exposed directly as an entitlement.