Skip to content

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.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes 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.
  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.

Note

The linked document is not maintained by SailPoint and is subject to change without notice.