---
title: "Atlassian Cloud (Jira)"
slug: "atlassian-jira-cloud"
updated: 2026-06-30T18:53:46Z
published: 2026-06-30T18:53:46Z
canonical: "help.claritysecurity.com/atlassian-jira-cloud"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.claritysecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Atlassian Cloud (Jira)

This guide will show you how to set up the integration between Atlassian Cloud (Jira) and Clarity Security.

**Estimated time to complete:** 15-30 minutes.

If you run into any problems, please contact your support team or [support@claritysecurity.io](mailto:support@claritysecurity.io).

---

## Before you begin

When performing the OAuth Login process, depending on the level of access the user has, you may experience limitations with what Clarity can import during a sync, or when performing User modifications.

| Level | Covers | Gaps |
| --- | --- | --- |
| **site-admins** | All 14 API calls | None — full coverage |
| **jira-administrators** | Read sync + project-role provisioning | Can't create/delete users or manage group membership |

**Key takeaways:**

- **site-admins:** only account type that covers everything — use this for any integration that provisions/deprovisions group membership or manages user lifecycle

- **jira-administrators:** sufficient for read-only sync + project-role provisioning — a viable scoped-down option if you're not touching users or groups

**Bottom line:** Use a site-admin OAuth account for full provisioning. Use **jira-administrators** only if the integration is explicitly scoped to read + project-role management with no user/group writes.

## **Configuring in your Downstream Application**

### **Step 1: Create an Atlassian Application**

Navigate to the My Apps Section in the Atlassian Developer Console:

[https://developer.atlassian.com/console/myapps/](https://developer.atlassian.com/console/myapps/) ![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(610).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

### **Step 2: Setup Distribution**

Setup Distribution in the new OAuth2 application from Step 1 to be “Sharing”

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(611).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

### **Step 3: Set Permissions**

Setup the OAuth2 application **Granular** permissions for Jira and grant the following scopes:

**Click Here for Scopes in a table (not image)**

| **Scope Name** | **Description** | **Code** |
| --- | --- | --- |
| View application roles | View application roles. | read:application-role:jira |
| View avatars | View system and custom avatars. | read:avatar:jira |
| View groups | View user groups. | read:group:jira |
| Create and update groups | Create and update user groups. | write:group:jira |
| View issue types | View issue types. | read:issue-type:jira |
| Read issue type hierarchies | Read issue type hierarchies. | read:issue-type-hierarchy:jira |
| View users | View users. | read:user:jira |
| Create and delete users | Create and delete Jira users. | write:user:jira |
| View user columns | View user columns. | read:user.columns:jira |
| View permissions | View permissions. | read:permission:jira |
| View projects | View projects. | read:project:jira |
| View project categories | View project categories. | read:project-category:jira |
| Create and update project categories | Create and update project categories. | write:project-category:jira |
| View project components | View project components. | read:project.component:jira |
| View project properties | View project properties. | read:project.property:jira |
| View project roles | View project roles. | read:project-role:jira |
| Create and update project roles | Create and update project roles. | write:project-role:jira |
| Delete project roles | Delete project roles. | delete:project-role:jira |
| View project versions | View project versions. | read:project-version:jira |
| View user properties | View user properties. | read:user.property:jira |
| View user configurations | View user configurations. | read:user-configuration:jira |
| View organization's users | View organization's users. | read:organization.user:jira-service-management |

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(612).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

## **Configuring the** **Integration** **within Clarity**

### **Step 4: Login to your Clarity Security tenant**

> https://your-tenant.claritysecurity.io/

### **Step 5: Click on Applications, then Marketplace**

![Applications > Marketplace](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679588491503.png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

### **Step 6: Find Atlassian Cloud Scroll to or search for Atlassian Cloud in the list of applications from the marketplace, then click** **Connect.**

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(613).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

### **Step 7: Connect App**

Complete the **Connect App** form. Details for fields common to all applications can be found at the following article: [Common App Configuration Steps](/docs/common-app-configuration-steps)

Get Atlassian Cloud marketplace application ready to copy over Site URL, Client ID, and Client Secret. ![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(614).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

## **Back in Atlassian**

### **Step 8: Get the Jira Site URL from the Admin Portal**

Navigate to the Apps tab from the Admin Portal and copy the Jira URL

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(615).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

### **Step 9: Set the Atlassian Oauth2 Application’s callback URL**

Copy the OAuth Redirect URL inside of Clarity and paste it into the callback URL field in Atlassian

Your URL will similar to this:

`https://YOUR_TENANT.claritysecurity.io/application/oauthProcessCode/atlassian-cloud`

> [!NOTE]
> URL Ending
> 
> The last part of the URL should match the **Unique Identifier** (`atlassian-cloud` is the default unique identifier when connecting your **first Atlassian Cloud**)

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(625).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(616).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(617).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

### **Step 10: Copy Client ID & Client Secret from Atlassian and paste them into Clarity**

Go into Atlassian OAuth2 application settings and copy the client ID and client secret into Clarity

![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image(621).png?sv=2026-02-06&spr=https&st=2026-11-09T19%3A22%3A30Z&se=2026-11-09T20%3A22%3A30Z&sr=c&sp=r&sig=typPje0aVntsKcSg%2BKYIAE%2B04OZqv3a4LyKSlJNnTQg%3D)

### **Step 11: App Settings**

Complete the **App Settings** form. Details for each field can be found at the following article: [Common App Configuration Steps](/docs/common-app-configuration-steps)

### **Step 12: User Settings**

Complete the **User Settings** form. Details for each field can be found at the following article: [Common App Configuration Steps](/docs/common-app-configuration-steps)

### **Step 13: Validate Your Selections and Save**

Validate the selections from Configure App Step 3, and hit the **Save** button.

**Save**

Clicking the **Save** button will trigger the first full sync for your application (even if you selected Manual syncing). This includes Service Users, Entitlements, Service User Entitlements, Service User Attributes.

## **Need Help?**

If you have any problems, contact your customer success team. You can also get in touch with our general support [via email](mailto:support@claritysecurity.io), open a [support ticket](https://support.claritysecurity.com/home). Our general support team is available Monday - Friday from 8:00 AM - 6:30 PM CST.

A Downstream Application is any application that supplies Clarity with service users, entitlements, and attributes.

An Integration is any application, service, or data source used in Clarity for pulling in information about your users and their access.

A Service User is a user, or service account, discovered by Clarity in a downstream application.

An Entitlement is an assignable permission found in a downstream application. Common examples include licenses, groups, and policies.

Service User Entitlements are the pairings of users and active entitlement access in downstream applications.

An attribute is a piece of information used to describe a service user, entitlement, or identity. Common examples include First Name, Last Name, Job Title, Department, etc.