> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ticketing-and-messaging/ticket-management/jira/jira-permissions.md).

# Jira Permissions

* **Permission name:** May differ, depending on your version of Jira. For on-premises Jira the permissions interface is similar to Jira Cloud, but the might look slightly different.
* **Project permissions:** Are configured in the project administration page and may differ, depending on their project permission scheme.
* **Cloud Jira:** Has specific team-managed projects, where permissions are defined for roles and then roles are assigned to users. Role permissions are similar to project level permissions defined in the permission scheme.\
  **Settings > Projects > Target Projects > Project Settings > Access > Manage Users/Roles**
* **Default permission scheme:** Grants access to add-on for all the members of administrators and developers groups. No additional configuration is required in this case.

## API Token Scopes (Jira Cloud)

When generating an API token in Atlassian for a dedicated service account, in case you are prompted to select scopes, assign the following:

| Scope             | Required for                                                          |
| ----------------- | --------------------------------------------------------------------- |
| `read:jira-work`  | Reading issues, comments, and worklogs.                               |
| `write:jira-work` | Creating and editing issues, posting comments, and creating worklogs. |

Missing or insufficient scopes will cause the connector to fail authentication, even when Jira user permissions are correctly configured.

## Project Level Permissions

To change, go to **Settings > Projects > Target Projects > Project Settings > Permissions**.

| **Permission Name** | **Code**            | **Purpose / Required For**                                                                   |
| ------------------- | ------------------- | -------------------------------------------------------------------------------------------- |
| **Browse Projects** | `BROWSE_PROJECTS`   | <p>- Viewing project information<br>- Searching projects<br>- Accessing project settings</p> |
| **Create Issues**   | `CREATE_ISSUES`     | <p>- Creating new issues<br>- Bulk issue creation</p>                                        |
| **Edit Issues**     | `EDIT_ISSUES`       | <p>- Updating existing issues<br>- Transitioning issues</p>                                  |
| **Comment Issues**  | `ADD_COMMENTS`      | - Adding comments to issues                                                                  |
| **Close Issues**    | `TRANSITION_ISSUES` | <p>- Closing/resolving issues<br>- Changing issue status</p>                                 |
| **Assign Issues**   | `ASSIGN_ISSUES`     | <p>- Changing issue assignees<br>- Assigning during issue creation</p>                       |

## Global Permissions

To change, go to **Settings > System > Global Permissions**.

| **Permission Name** | **Code**       | **Purpose / Required For**                             |
| ------------------- | -------------- | ------------------------------------------------------ |
| **Browse Users**    | `BROWSE_USERS` | <p>- Searching users<br>- Viewing user information</p> |

## Additional Jira Cloud Requirements

To ensure a successful integration with Jira Cloud, the user whose credentials are used during the connector integration process, must have the **User** role for the relevant Jira product.

Most Jira projects are associated with either Jira Software or Jira Service Management. To prevent integration issues, assign the **User** role to the user for both products. This role provides the necessary permissions to make API calls.

**To check your user role:**

1. Sign in to Jira Cloud as an administrator.\
   Make sure you have the required permissions to manage users.
2. Go to **Settings** > **User Management**.
3. Search for the user whose credentials are used in the connectors.
4. Select the username to open their profile.
5. Under **Product Access**, confirm that the user has access to the relevant Jira product.
6. Verify that the user role is set to **User** for the applicable product.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ox.security/ticketing-and-messaging/ticket-management/jira/jira-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.