# Integrating SailPoint with MeisterTask

MeisterTask is a collaborative task and project management application. Its public REST API exposes the people on a team, the team groups those people belong to, and the projects they can access. This document covers how to configure a new direct connection between SailPoint and MeisterTask 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 MeisterTask connector supports the following:

### Account Management

- Aggregate Persons

### Entitlement Management

- Aggregate Groups

> [!NOTE]
>
> This connector is read-only. It supports test connection, account aggregation, and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported.

> [!NOTE]
>
> Group aggregation requires a MeisterTask Business plan. `GET /api/groups` is documented as Business plan only.

> [!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 MeisterTask connector, ensure the following requirements are met:

1. Create a MeisterTask personal access token, or register an OAuth 2.0 client. MeisterTask uses MindMeister for OAuth application and token management.
2. Select the OAuth scopes `userinfo.profile`, `userinfo.email`, and `meistertask` on the token or client.
3. Confirm the API host. Every documented call uses `https://www.meistertask.com`. The API base path is `/api`.
4. Copy and securely store the Base URL and the access token. Store the token value only. The HTTP operation adds the Bearer prefix.

For more information, refer to the [MeisterTask developer documentation](<https://developers.meistertask.com/>).

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

## Required Permissions

The token must be able to call `GET /api/persons`. Group aggregation additionally requires a MeisterTask Business plan.

- **Team Admin** - Required to create user groups and to manage who belongs to them. Groups are created in MeisterTask from the avatar menu: **Account \> My Team \> + Add Group**. Drag a person into the group. MeisterTask assigns the group id; it is not entered manually.
- **Team Member** - Can collaborate on projects and tasks. A member token can aggregate persons the token can see. It cannot administer team groups.
- **Content Manager** and **Viewer** - Seat types on the team. They control whether a person can edit MeisterTask content. They are not the project role ids returned by the API.

> [!NOTE]
>
> Projects such as Development and Test are not groups. A project membership does not add a value to `group_ids`. Project roles are documented separately because MeisterTask does not expose a role collection.