# SailPoint Atlassian Suite SaaS Connector Documentation

> Atlassian Suite SaaS Connector Documentation

# Documentation

# Connecting SailPoint and Atlassian Suite SaaS

To connect SailPoint with Atlassian Suite, perform the following tasks:

## Adding 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.

> [!IMPORTANT]
>
> By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration.

**To configure a new source:**

1. Sign in to SailPoint.
2. Go to **Admin \> Connections \> Sources**.
3. Select **Create New**.
4. Search for the connector by entering the name in the search box, and then select **Actions**.
5. In the **Actions** dropdown list, select the setup method:

   - [**Express Setup**](<#configuring-a-source-using-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**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Configuring a Source Using Express Setup

Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data.

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**
   >
   > The source name must be unique. You can change these settings later in the source configuration.
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** section.
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.

### Configuring a Source Using Standard Setup

Use Standard Setup to configure the connector for full feature support.

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. Continue to configure your connected source there.

## 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 unique name and description for the source.
2. In the **Source Owner** dropdown list, select the identity that owns this source.

   - To find a source owner, begin entering their name.
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, 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. Refer to [Connection Settings](<#connection-settings>) for more information.
5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. 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>).
6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.

   - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system.
   - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.
7. Select **Save**.

## Connection Settings

Provide the information required for SailPoint to connect and authenticate with Atlassian Suite Cloud.

1. Enter the **Site URL** (HTTPS API URL) for the cloud instance. For example:

   `https://contoso.atlassian.net`
2. Enter the **Email Address** of the Atlassian Jira instance administrator account that you want to configure to execute transactions.
3. Choose the appropriate Authentication Type and provide the information required to connect and interact with the source. The following Authentication Types are supported:

   - Basic
   - Service Account

### Basic Authentication

1. Enter the **Email Address** of the Atlassian Jira instance administrator account that you want to configure to execute transactions.
2. Enter the **Site Admin API Token** for the instance administrator. The Site Admin API Token is generated in the source.

   For more information, refer to [Manage API tokens for your Atlassian account](<https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/>) in the Atlassian documentation.

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

   > **Note**
   >
   > Atlassian API tokens don’t use selectable scopes like OAuth scopes. They inherit the creator’s Atlassian roles, so use an account with the required admin role when creating the token. Create the API token without scope.

> [!NOTE]
>
> **Screenshot**
>
> [![Basic Authentication connection settings](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/basic_authentication_1.png>)](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/basic_authentication_1.png>)

### Service Account Authentication

1. Enter the Email Address of the Atlassian Jira service account.
2. Enter the **Service Account API Token**.
3. Use a scoped API token generated for a service account that has Jira product access and the required permissions. The token must include these classic scopes:

   - `read:jira-work`
   - `read:jira-user`
   - `manage:jira-configuration`
   - `manage:jira-project`

   For more information, refer to [Manage API tokens for service accounts](<https://support.atlassian.com/user-management/docs/manage-api-tokens-for-service-accounts/>).
4. (Optional) Enter **Confluence Scoped API Token** for NHI Discovery from Confluence.

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

> [!NOTE]
>
> **Screenshot**
>
> [![Service Account Authentication connection settings](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/service_account_authentication.png>)](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/service_account_authentication.png>)

Once the Authentication Type is selected perform the following steps:

1. (Optional) Enter the **Org Admin API Token** for the instance administrator. This is required to enable, disable accounts or discover Non Human Identities. The Org Admin API Token is generated in the source.

   For more information, refer to [Manage an organization with the admin APIs](<https://support.atlassian.com/organization-administration/docs/manage-an-organization-with-the-admin-apis/>) in the Atlassian documentation.

   > **Note**
   >
   > The linked document is not maintained by SailPoint and is subject to change without notice.
2. (Optional) Enter the **Connection Timeout** (in minutes) to hold the connection with the Atlassian system in an idle state. The default is 1 minute.
3. Select **Save**.

## Activity Insights Settings

SailPoint pulls in activity data in the form of events like user logins, password changes, and content updates within the application. You can view an identity’s activity data within an application to discover trends for that user.

> [!IMPORTANT]
>
> Contact your SailPoint Customer Success Manager (CSM) for more information on Activity Insights. For more information on utilizing activity data, refer to [Activity Insights](<https://documentation.sailpoint.com/saas/help/ai/activity_insights/index.html>).

Activity Insights Settings allows you to gather account information and activity data from Atlassian Suite. To enable Activity Insights for the Atlassian Suite application, refer to [Prerequisites](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/index.html#prerequisites>) for more information.

To configure Activity Insights, complete the following:

> [!NOTE]
>
> **Screenshot**
>
> [![Activity Insights Settings](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/common/assets/img/activity_insights.png>)](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/common/assets/img/activity_insights.png>)

1. Go to **Activity Insights Settings**.
2. Select **Enable Activity Insights** to view access to data insights on source and application activity such as logins and other app-specific events.
3. Select **Save**.

## Aggregation Settings

Configure the aggregation parameters such as filter conditions and page size. Use a semicolon delimiter to add multiple filter conditions.

For more information about aggregation, refer to [Loading Account Data](<https://documentation.sailpoint.com/saas/help/accounts/loading_data.html>).

> [!NOTE]
>
> **Screenshot**
>
> [![alt text](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_add1.png>)](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_add1.png>)

1. Go to **Additional Settings \> Aggregation Settings**.
2. (Optional) Select **Aggregate Inactive Users** to aggregate inactive users along with active users.
3. (Optional) Enter or paste the **Account Filter** to filter accounts during aggregation. Only strings are supported as a filter condition. For multiple conditions, use a semicolon delimiter. For example:

   - For single conditions, `john` aggregates only those accounts whose display name or email prefix contain the name john.
   - For multiple conditions, `john;chris` aggregates all users whose display name or email prefix are john or chris.
4. (Optional) In the **Page Size** field, enter the number of records to fetch per page. The default is 50 records per page. The minimum value is 1 and the maximum is 1000.

> [!NOTE]
>
> To perform enable or disable operations on inactive users, the Aggregate Inactive option on UI must be enabled.

1. Select **Save**.

### Advanced Settings

In this section, you can provide settings for API Version, Thread Count, and Connection Timeout.

> [!NOTE]
>
> SailPoint recommends that you do not change the default settings. Changing the settings could result in performance issues.

> [!NOTE]
>
> **Screenshot**
>
> [![alt text](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_add2.png>)](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_add2.png>)

1. Go to **Additional Settings \> Advanced Settings**.
2. (Optional) Select the **API Version** to use for the connection. The default is 2.
3. (Optional) In the **Thread Count** field, specify the maximum number of threads for account aggregation. The default is 8.
4. (Optional) Enter the **Connection Timeout in Minutes** to hold the HTTP connection with the Atlassian system in an idle state. The default is 1 minute.
5. 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.

# Dataset Management

Dataset Management lets you review the object types a source collects and control how the source aggregates those objects into SailPoint. Use Dataset Management to view and manage resource attributes, datasets and their resources, enable dataset aggregation schedules, perform manual aggregation, and view aggregation history.

> [!NOTE]
>
> Datasets are also available in SailPoint Agentic Fabric. Contact your Customer Success team and refer to [SailPoint Agentic Fabric](<https://documentation.sailpoint.com/saas/help/agentic_fabric/index.html>) for more information.

For more information, refer to [Managing Datasets and Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html>) for datasets, resources, owner correlation, and aggregation.

## Datasets

A *dataset* is a named group of one or more related resources that the source aggregates together.

When aggregation runs for a dataset, the source collects all resources in that dataset from the managed system in one aggregation job. Activate or deactivate aggregation at the dataset level, not for individual resources.

> [!NOTE]
>
> Each resource belongs to exactly one dataset for that source. The source defines which resources belong to each dataset. You can enable aggregation and review associated resources, but you cannot create or delete datasets or move resources between them.

### Dataset Aggregation

Configure aggregation on the **Dataset Aggregations** tab for each dataset. Configure each dataset separately. During aggregation, your owner correlation rules are automatically applied to link machine identities to their human owners. For more information, refer to [Configuring Dataset Aggregations](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#configuring-dataset-aggregations>).

## Resources

A resource defines an object type from the managed system. It specifies the kind of object, the attributes the source collects, and how the source identifies and displays each object. Resources form the building blocks of the data model.

In the UI, each resource appears under **Dataset Management** \> **Resources** with its schema. A resource does not run aggregation by itself. The dataset that owns the resource collects it during aggregation.

For more information, refer to [Managing Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#managing-resources>).

### Owner Correlation

Configure owner correlation on each resource to link aggregated objects to human owners. If you do not configure owner correlation, or if the mapping produces no match, an owner is not assigned. For more information, refer to [Configuring Owner Correlation](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#configuring-owner-correlation>).

## Supported Datasets

Go to **Dataset Management \> Datasets** on your Atlassian Suite SaaS source to view the datasets the connector aggregates. Select a dataset to review its associated resources and configure aggregation.

> [!NOTE]
>
> Configure aggregation for each dataset separately. For more information, refer to [Dataset Aggregation](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#configuring-dataset-aggregations>).

The connector collects Atlassian Cloud users, groups, and project roles as accounts and entitlements. It collects Atlassian Cloud service accounts, agents, and application accounts in the Atlassian Cloud Service Accounts and Agents dataset using Dataset 2.0 Resource Modelling.

| Dataset name | Dataset ID | Associated resources | Required license | Default schedule |
| --- | --- | --- | --- | --- |
| Atlassian Cloud Service Accounts and Agents | `atlassian:cloud-service-accounts` | Atlassian Cloud Service Account, Atlassian Cloud Agent, Atlassian Cloud Application Account | SailPoint Agentic Fabric | Every 12 hours |

## Supported Resources

The connector collects Atlassian Cloud users, groups, and project roles as accounts and entitlements. It collects Atlassian Cloud service accounts, agents, and application accounts in the Atlassian Cloud Service Accounts and Agents dataset using Dataset 2.0 Resource Modelling.

For more information, refer to [Managing Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#managing-resources>).

> [!NOTE]
>
> When you enable dataset aggregation for a selected dataset, all resources in that dataset are collected at once. Activate or deactivate aggregation at the dataset level, not for individual resources.

### Atlassian Cloud Service Accounts and Agents

The Atlassian Cloud Service Accounts and Agents dataset contains the following resources:

| Resource name | Resource type | Resource ID |
| --- | --- | --- |
| Atlassian Cloud Service Account | Account (`std:account`) | `atlassian:cloud-service-account` |
| Atlassian Cloud Agent | Agent (`std:agent`) | `atlassian:cloud-agent` |
| Atlassian Cloud Application Account | Account (`std:account`) | `atlassian:cloud-application-account` |

For more information on schema attribute details, refer to:

- [Atlassian Cloud Service Account Attributes](<#atlassian-cloud-service-account-attributes>)
- [Atlassian Cloud Agent Attributes](<#atlassian-cloud-agent-attributes>)
- [Atlassian Cloud Application Account Attributes](<#atlassian-cloud-application-account-attributes>)

## Atlassian Cloud Service Account Attributes

Schema attributes for the Atlassian Cloud Service Account resource.

- Resource ID: `atlassian:cloud-service-account`
- Resource type: `std:account`
- Classification: machine
- Identity attribute: `accountId`
- Display attribute: `displayName`

| Attribute | Type | Description |
| --- | --- | --- |
| identity | string | The Atlassian account ID of the service account. Same value as `accountId`. |
| accountId | string | Unique identifier of the Atlassian app principal. |
| accountType | string | Principal type. Always `app` in this dataset. |
| appType | string | App subtype of the principal, for example service |
| displayName | string | Display name of the app or bot principal. |
| active | boolean | Whether the app principal is active. |

## Atlassian Cloud Agent Attributes

Schema attributes for the Atlassian Cloud Agent resource.

- Resource ID: `atlassian:cloud-agent`
- Resource type: `std:agent`
- Identity attribute: `accountId`
- Display attribute: `displayName`

| Attribute | Type | Description |
| --- | --- | --- |
| identity | string | The Atlassian account ID of the agent. Same value as `accountId`. |
| accountId | string | Unique identifier of the Atlassian Cloud agent. |
| accountType | string | Account type. Always `app` for Atlassian Cloud agents. |
| appType | string | App subtype of the agent, for example `agent`. |
| displayName | string | Display name of the Atlassian Cloud agent. |
| active | boolean | Whether the agent is active. |

## Atlassian Cloud Application Account Attributes

Schema attributes for the Atlassian Cloud Application Account resource. This resource does not include `appType`.

- Resource ID: `atlassian:cloud-application-account`
- Resource type: `std:account`
- Classification: machine
- Identity attribute: `accountId`
- Display attribute: `displayName`

| Attribute | Type | Description |
| --- | --- | --- |
| identity | string | The Atlassian account ID of the application account. Same value as `accountId`. |
| accountId | string | Unique identifier of the Atlassian Cloud application account. |
| accountType | string | Account type. Always app for Atlassian Cloud application accounts. |
| displayName | string | Display name of the Atlassian Cloud application account. |
| active | boolean | Whether the application account is active. |

# Enable Direct Permissions

Direct permission is a right an admin gets that provides detailed access to other accounts. It allows rights to create, read, or update an object such as a file or an application.

Enabling direct permission with an entitlement improves governance insights, such as:

- Allows admins to see what actions a user can perform with the access granted by an entitlement.
- Allows admins to create more effective access profiles and roles.
- Allows reviewers to make necessary decisions on certifications.

# Integrating SailPoint with Atlassian Suite SaaS

Atlassian is a leading product company providing tools for collaboration and service desk. SailPoint's Atlassian Suite SaaS connector supports reading and provisioning of Atlassian users and groups. Use the Atlassian Suite SaaS source to manage Atlassian Suite user accounts. After it is successfully configured, your organization is able to aggregate and provision accounts for Jira users and manage access to other Atlassian Suite products such as Confluence and Jira Service Management by managing memberships of groups having access to the respective products.

This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of the Atlassian Suite SaaS source.

> [!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 Atlassian Suite SaaS connector supports the features listed on this page.

> [!NOTE]
>
> Before you can use any feature marked with an asterisk (\*), SailPoint must activate the feature for your site.

### Account Management

- Aggregate accounts
- Add and remove entitlements
- \*Provision accounts

  - Create new accounts
  - Enable and disable managed accounts

    > **Note**
    >
    > Accounts must be claimed accounts from verified domains. For more information, refer to [Claim accounts](<https://support.atlassian.com/user-management/docs/verify-a-domain-to-manage-accounts/#Claim-accounts>) and [Verified domains in your organization](<https://support.atlassian.com/user-management/docs/verify-a-domain-to-manage-accounts/#Verified-domains-in-your-organization>) in the Atlassian documentation. Atlassian documentation is not managed by SailPoint and is subject to change without notice.
- \*Access Certifications (certification of entitlements connected to accounts)
- Multiple Group Objects and Direct Permissions
- Delete Accounts

For more information on features, refer to [Source Features](<https://community.sailpoint.com/knowledge/Identity-Security-Cloud-Source-Features>).

The following table lists the account feature details:

| Feature | Users |
| --- | --- |
| Aggregate | ✔ |
| Create | ✔ |
| Group Entitlements (Read, Request, Revoke) | Groups and Project Roles |
| Enable Direct Permissions | ✔ |

### Group Entitlements

Group Entitlements enable SailPoint to aggregate additional details from the managed system. These objects have a separate schema attribute definition list that the aggregation fetches when aggregation is run for that Group Entitlement type.

The following table lists the group feature details:

| Feature | Groups | Project Roles |
| --- | --- | --- |
| Aggregation | ✔ | ✔ |

### Non-Human Identity Discovery

- Aggregate Atlassian Cloud service accounts and agents

Refer to Dataset Management for more information.

Refer to [Discovering Potential Non-Human Accounts](<https://documentation.sailpoint.com/saas/help/agentic_fabric/nhi/non_human_accounts.html#discovering-potential-non-human-accounts>) for more information.

### Activity Insights

Activity Insights supports activity from Atlassian Suite and its associated accounts. This allows you to gather account information and activity data from Atlassian Suite.

> [!IMPORTANT]
>
> Contact your SailPoint Customer Success Manager (CSM) for more information on Activity Insights. For more information on configuring Activity Insights, refer to Activity Insights Settings.

## Supported Managed Systems

The SailPoint Atlassian Suite SaaS connector supports the following Atlassian products:

- Jira Software (Cloud)
- Jira Service Management
- Opsgenie
- Statuspage
- Confluence

> [!NOTE]
>
> The Jira Administrator can manage the Default Access group associated with different products. Users created from SailPoint are automatically assigned to the default Product Access Groups enabled on the managed system.

## Prerequisites

- The client is authorized using basic authentication which uses a Site Admin API Token. The token is encoded, and it is generated by user account with **Site Admin** access. It is added to headers for API requests.

  For more information on generating Site Admin API tokens, refer to [Manage API tokens for your Atlassian account](<https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/>) in the Atlassian documentation.

  > **Note**
  >
  > Atlassian API tokens don't use selectable scopes like OAuth scopes. They inherit the creator's Atlassian roles, so use an account with the required admin role when creating the token. Create the API token without a scope.
- Enabling or disabling accounts uses token authentication. It needs an Org Admin API Token generated by a user with **Org and Site Admin** access.

  For more information on generating API tokens, refer to [Manage an organization with the admin APIs](<https://support.atlassian.com/organization-administration/docs/manage-an-organization-with-the-admin-apis/>) in the Atlassian documentation.

  > **Note**
  >
  > Atlassian API tokens don't use selectable scopes like OAuth scopes. They inherit the creator's Atlassian roles, so use an account with the required admin role when creating the token. Create the API token without a scope. The linked document is not maintained by SailPoint and is subject to change without notice.

  > **Screenshot**
  >
  > [![API key without scopes selection](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_before_you_begin.png>)](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_before_you_begin.png>)

### For Basic Authentication

The client is authorized using basic authentication which uses a Site Admin API Token. The token is encoded, and it is generated by user account with Site Admin access. It is added to headers for API requests.

For more information on generating Site Admin API tokens, refer to [Manage API tokens for your Atlassian account](<https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/>).

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

> [!NOTE]
>
> **Screenshot**
>
> [![API Tokens](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_api_token.png>)](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/img/atl_suite_c_api_token.png>)

### For Service Account Authentication

- The client is authorized using the email address of an Atlassian service account and a Service Account API Token. Use a scoped API token generated for a service account that has Jira product access and the required permissions. The token must include these classic scopes:

  - `read:jira-work`
  - `read:jira-user`
  - `manage:jira-configuration`
  - `manage:jira-project`

  For more information, refer to [Manage API tokens for service accounts](<https://support.atlassian.com/user-management/docs/manage-api-tokens-for-service-accounts/>).

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

### For Activity Insights

- Configure **Organization ID** which is the unique identifier of the organization of Atlassian tenant. For more information, refer to [Manage an organization with the admin APIs](<https://support.atlassian.com/organization-administration/docs/manage-an-organization-with-the-admin-apis/>) in the Atlassian documentation.
- Configure **Org Admin API Token** to enable activity insights. For more information, refer to [Connection Settings](<https://documentation.sailpoint.com/connectors/atl_cloud/saas/help/connecting.html>).

## Required Permissions

- The service account must be a Site Admin User (Site Admin/ jira-administrators) with an API token created on the Atlassian Suite managed target system.
- To support enabling and disabling accounts, the service account must be a Org and Site Admin User with an Org Admin API token created on the Atlassian Suite managed target system.

## Onboard Atlassian Suite SaaS with SailPoint Agentic Fabric (SAF)

SailPoint Agentic Fabric (SAF) provides an automated, guided onboarding experience to connect your Atlassian Suite environment to SailPoint. SAF automatically creates, deploys, and configures the Atlassian Suite SaaS source in SailPoint, reducing the manual setup steps. After onboarding, the source is ready for aggregation and governance.

For detailed onboarding instructions, prerequisites, and supported deployment models, refer to [Connecting Sources](<https://documentation.sailpoint.com/saas/help/agentic_fabric/onboarding/sources.html>).

> [!IMPORTANT]
>
> To enable advanced governance capabilities for Atlassian Suite resources and AI agents, an active SailPoint Agentic Fabric Advanced Governance license is required. Contact your SailPoint Customer Success Manager to request access and for more information.

# Provisioning

The Atlassian Suite SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in Atlassian Suite directly from SailPoint.

**Prerequisite:** Your system is configured for provisioning.

When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*.

When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment.

For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account.

> [!IMPORTANT]
>
> This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail.

## Default Create Account Attributes

The following generators create the required information for a new Atlassian Suite SaaS account:

| Account Attributes | Identity Attribute | Description |
| --- | --- | --- |
| emailAddress | Work Email | The email address of the user<br><br>**Note**: If there is any issue with the aggregation of the `emailAddress` attribute, note that the `emailAddress` attribute is aggregated only for accounts from those domains that belong to the service account's domain. |
| displayName | Display Name | The display name of the user |

> [!NOTE]
>
> For more information on setting the mapping types, refer to [Editing the Account Creation Configuration](<https://documentation.sailpoint.com/saas/help/provisioning/create_profile.html#editing-the-account-creation-configuration>).

# 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 Atlassian Suite SaaS connector uses the following default correlation and object configurations.

## Default Correlation Configuration

Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements.

You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities](<https://documentation.sailpoint.com/saas/help/accounts/correlation.html>) for more information.

When you first create the Atlassian Suite SaaS source, the default correlation mapping is:

| Account Attribute | Operation | Identity Attribute |
| --- | --- | --- |
| emailAddress | Equals | Work Email (email) |
| displayName | Equals | displayname |

## 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 |
| --- | --- |
| accountId | Account |
| name | Group |
| projectRoleId | Project Role |

### Default Account Attributes

The Atlassian Suite SaaS 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 |
| --- | --- |
| accountId | A unique identifier for an Atlassian user. This is an Account ID which must not be changed. |
| accountType | The type of account that the user belongs to. |
| displayName | The display name of the user. |
| emailAddress | The email address of the user. |
| timeZone | The timezone of the user. |
| locale | The default location of the user for purpose of localizing items. |
| groups | The list of groups that the user belongs to. |
| projectRoles | The list of roles that the user belongs to. |

> [!NOTE]
>
> The `emailAddress` attribute is only fetched for accounts in the same domain as the service account.

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

The Atlassian Suite SaaS connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.

| Attribute Name | Description |
| --- | --- |
| groupId | A unique identifier for the group. |
| name | The name of the group. This is an Account ID which must not be changed. |
| labels | The description (labels) of the group. |

### Default Project Role Attributes

| Attribute Name | Description |
| --- | --- |
| name | The name of the project role. |
| displayName | The display name of the project role. |
| projectRoleId | A unique identifier for the project specific roles combining Role ID and its corresponding Project ID. This is an Account ID which must not be changed. |
| id | A unique identifier for the project role. |
| description | The description of the project role. |

# Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

- [SailPoint Identity Services Documentation](<https://documentation.sailpoint.com/saas/help/index.html>)
- [SailPoint Support Knowledge Base](<https://support.sailpoint.com/csm?id=kb_view2&amp;kb_id=05ff44289f011200550bf7b6077fcfa3>)
- [SailPoint Developer Community](<https://developer.sailpoint.com/>)

## Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](<https://documentation.sailpoint.com/saas/help/sources/managing_additional_settings.html>).

## Enabling or Disabling an Account Fails

**Issue**: Enabling/disabling an account fails with the error: `Error while disabling account: Unauthorized`

**Resolution**: Cross-check the attribute encrypted in the source config and verify whether the `adminApiToken` is missing in the value section. Then append the `adminApiToken` values using the following API request.

Add the following entry to the source using the SailPoint REST APIs:

`PATCH 'https://{orgName}.api.sailpoint.com/v3/sources/<source-id>'`

In the body of the `PATCH`, use the raw-data as follows:

```javascript
{
        "op": "add",
        "path": "/connectorAttributes/encrypted",
        "value":  "apiToken,adminApiToken"
    }
```

## Command Times Out During Provision or Enable/Disable Operations

**Issue**: A command times out during provision or enable/disable operations.

**Resolution**: Set the `provisioningTimeout` attribute to `600`.

Update the provisioningTimeout attribute as follows:

```javascript
[
    {
        "op": "add",
        "path": "/connectorAttributes/provisioningTimeout",
        "value": 600
    }
]
```

## Single Account Aggregation Failure Involving the ProjectRole Attribute

**Issue**: Single account aggregation fails when the entitlement attribute `ProjectRole` is present in the account schema.

**Resolution**: Add the following entry to ensure that membership aggregation of Project Roles is skipped with the ResourceObject (RO) as incomplete. Sending the RO as incomplete ensures that the existing Project Role assignments are not removed from SailPoint. Full aggregation is not impacted by this entry.

```javascript
key : skipProjectRoleForGetObject
value : true
```

## Project Role Entitlement Aggregation Failure; Stream Timeout

**Issue**: Entitlement aggregation fails for object type `ProjectRole` with:

`An internal error occurred handling stream response from the server`

This happens when Project Role aggregation runs longer than the default stream timeout. The connector must walk projects and their roles before returning the stream, so large sites can exceed the limit.

**Resolution**: Increase the aggregation timeout on the source so the Project Role stream can complete. Account aggregation and other entitlement types are not affected by this entry.

```javascript
key: aggregateTimeout
value: 3600
```