# Integrating SailPoint with Fibery

Fibery is a connected workspace for work management and knowledge base use cases. It manages users and roles. This document covers how to configure a new direct connection between SailPoint and Fibery for Quick Compliance. 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 Fibery connector supports the following:

### Account Management

- Aggregate Users

> [!NOTE]
>
> This connector is read-only. It supports test connection and account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported. There is no separate roles or groups query. Role is an entitlement on the account from the user `fibery/role` field. This source does not aggregate `fibery/user-group`.

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

Before you configure the Fibery connector, ensure the following requirements are met:

1. Sign in to Fibery. The workspace URL uses a specific pattern. For example, `https://<workspace>.fibery.io`.
2. Create or copy a personal API token (**Settings \> API tokens**). The connector sends `Authorization: Token <token>`.
3. Record the following values for connector configuration:

   - **Base URL**
   - **API Token**

> [!NOTE]
>
> - Authentication type is Custom Authentication (or API Token, depending on the source form). Do not use OAuth 2.0 or client credentials.
> - Every operation uses `Content-Type: application/json`.

## Required Permissions

Aggregation is read-only. The token must be able to query `fibery/user`. Roles observed include `role/admin`, `role/member`, and `role/observer`. For more information about Fibery, refer to the [official Fibery API documentation](<https://developers.fibery.com/>).

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