# SailPoint ProjectManager Connector Documentation

> ProjectManager Connector Documentation

# Documentation

# Connecting SailPoint and ProjectManager

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 ProjectManager host URL as **Base URL**. For example, `https://api.projectmanager.com/api/data`.
2. Enter **API Token**.
3. Select **Save**.

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

ProjectManager is a cloud-based project and work management platform that helps organizations plan, track, and manage projects efficiently. It provides capabilities for task management, resource allocation, time tracking, collaboration, and reporting, enabling teams to deliver projects on time and within budget. This document provides instructions to configure a new direct connection to a ProjectManager 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 ProjectManager connector supports the following:

### Account Management

- Aggregate active users

### Entitlement Management

- Aggregate Roles
- Aggregate Teams
- Aggregate Skills

> [!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 connector, generate an API token in ProjectManager.com.
- The ProjectManager connector uses Bearer token authentication.
- All API requests require a valid token.
- Only users with **Admin** or **Global Admin** privileges can generate API tokens.

  > **Resource Link**
  >
  > Resource Link [Generating an API Token](<https://developer.projectmanager.com/getting-started/authentication>)

## Required Permissions

To authenticate and call APIs using the ProjectManager connector, you need the appropriate permissions in your ProjectManager.com workspace.

- API Key Creation: Only users with **Admin** or **Global Admin** roles can create API keys. Users with lower privilege roles cannot generate API keys.
- API Key Scope: API keys are scoped at the workspace level. Keys allow access only to data and operations that the creating user is authorized to perform within that workspace.

  > **Note**
  >
  > ProjectManager.com does not offer dedicated service accounts or separate machine identities with granular API permissions. API key creation is restricted to **Admin** and **Global Admin** roles only.

  > **Important**
  >
  > Related Resources
  >
  > [Authentication and API Keys](<https://developer.projectmanager.com/getting-started/authentication>) | [API access overview](<https://developer.projectmanager.com/getting-started/overview>) | [API Key Scopes](<https://developer.projectmanager.com/api-reference/api-key/create-api-key>)

# 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 ProjectManager 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 ProjectManager 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 ID for the user |
| email | Email address of the user |
| firstName | First name of the user |
| lastName | Last name of the user |
| name | Full name of the user |
| initials | Initials of the user |
| isActive | Indicates whether the user account is active |
| role | Role assigned to the user |
| lastLogin | Date and time of the user's last login |
| phoneNumber | Contact phone number of the user |
| createdDate | Date and time when the user account was created |
| modifiedDate | Date and time when the user account was last modified |
| createdBy | ID of the user who created this account |
| modifiedBy | ID of the user who last modified this account |
| hourlyRate | Hourly rate for the user |
| city | City where the user is located |
| state | State or region where the user is located |
| country | Country code where the user is located |
| countryName | Name of the country |
| language | Language preference for the user |
| notes | Free-form notes about the user |
| colorName | Collaboration color assigned to the user |
| color | Hex value corresponding to the collaboration color |
| approver.id | Unique ID of the resource approver |
| approver.name | Name of the resource approver |
| teams.id | Teams associated with the user |
| skills.id | Skills associated with the user |

## 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 Role Attributes

The ProjectManager connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.

| Attribute Name | Description |
| --- | --- |
| id | Unique ID of the role |
| name | Name of the role |
| description | Description of the role |
| isAdmin | Indicates whether the role has admin privileges |
| isCustom | Indicates whether the role is custom-defined |
| isGlobalAdmin | Indicates whether the role is a global administrator |
| isGuest | Indicates whether the role is a guest role |
| isDefault | Indicates whether this is a default role |
| permissions.invitePeople.description | Description of invite people permission |
| permissions.invitePeople.value | Indicates whether the role can invite people |
| permissions.invitePeople.canBeModified | Indicates whether the permission can be modified |
| permissions.editAccountPage.description | Description of edit account page permission |
| permissions.editAccountPage.value | Indicates whether the role can edit the account page |
| permissions.editAccountPage.canBeModified | Indicates whether the permission can be modified |
| permissions.editSecurityPage.description | Description of edit security page permission |
| permissions.editSecurityPage.value | Indicates whether the role can edit the security page |
| permissions.editSecurityPage.canBeModified | Indicates whether the permission can be modified |
| permissions.seeHourlyRatesCostsBudgets.description | Description of permission to view rates and budgets |
| permissions.seeHourlyRatesCostsBudgets.value | Indicates whether the role can view rates and budgets |
| permissions.seeHourlyRatesCostsBudgets.canBeModified | Indicates whether the permission can be modified |
| permissions.setTeamHolidays.description | Description of set team holidays permission |
| permissions.setTeamHolidays.value | Indicates whether the role can set team holidays |
| permissions.setTeamHolidays.canBeModified | Indicates whether the permission can be modified |
| permissions.editTagsSkillsTeams.description | Description of edit tags, skills, and teams permission |
| permissions.editTagsSkillsTeams.value | Indicates whether the role can edit tags, skills, and teams |
| permissions.editTagsSkillsTeams.canBeModified | Indicates whether the permission can be modified |
| permissions.editTeamTimesheets.description | Description of edit team timesheets permission |
| permissions.editTeamTimesheets.value | Indicates whether the role can edit team timesheets |
| permissions.editTeamTimesheets.canBeModified | Indicates whether the permission can be modified |
| permissions.approveTimesheets.description | Description of approve timesheets permission |
| permissions.approveTimesheets.value | Indicates whether the role can approve timesheets |
| permissions.approveTimesheets.canBeModified | Indicates whether the permission can be modified |
| permissions.editImportantProjectInfo.description | Description of edit project info permission |
| permissions.editImportantProjectInfo.value | Indicates whether the role can edit important project information |
| permissions.editImportantProjectInfo.canBeModified | Indicates whether the permission can be modified |
| permissions.seeExportProject.description | Description of view/export project permission |
| permissions.seeExportProject.value | Indicates whether the role can view/export projects |
| permissions.seeExportProject.canBeModified | Indicates whether the permission can be modified |
| permissions.seeManageUsers.description | Description of manage users permission |
| permissions.seeManageUsers.value | Indicates whether the role can manage users |
| permissions.seeManageUsers.canBeModified | Indicates whether the permission can be modified |
| permissions.manageIntegrations.description | Description of manage integrations permission |
| permissions.manageIntegrations.value | Indicates whether the role can manage integrations |
| permissions.manageIntegrations.canBeModified | Indicates whether the permission can be modified |
| permissions.createProjectAndProjectGroups.description | Description of create projects permission |
| permissions.createProjectAndProjectGroups.value | Indicates whether the role can create projects |
| permissions.createProjectAndProjectGroups.canBeModified | Indicates whether the permission can be modified |
| permissions.editUsers.description | Description of edit users permission |
| permissions.editUsers.value | Indicates whether the role can edit users |
| permissions.editUsers.canBeModified | Indicates whether the permission can be modified |
| permissions.viewPersonalBoard.description | Description of view personal board permission |
| permissions.viewPersonalBoard.value | Indicates whether the role can view the personal board |
| permissions.viewPersonalBoard.canBeModified | Indicates whether the permission can be modified |
| permissions.editAllProjects.description | Description of edit all projects permission |
| permissions.editAllProjects.value | Indicates whether the role can edit all projects |
| permissions.editAllProjects.canBeModified | Indicates whether the permission can be modified |
| permissions.changeOwnEmail.description | Description of change own email permission |
| permissions.changeOwnEmail.value | Indicates whether the role can change own email |
| permissions.changeOwnEmail.canBeModified | Indicates whether the permission can be modified |

### Skill Attributes

| Attribute Name | Description |
| --- | --- |
| id | Unique ID of the skill |
| name | Name of the skill |
| inUse | Indicates whether the skill is currently in use |

### Default Team Attributes

| Attribute Name | Description |
| --- | --- |
| id | Unique ID of the team |
| name | Name of the team |