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

# Required Jira Permissions

> Reference for the project-level Jira permissions your connected Atlassian account needs so DinoAI can fully browse, create, transition, and comment on issues.

The Jira Tool can create, update, transition, assign, and comment on issues, so a **read-only token is not enough** to use its full capabilities.

The Jira account connected to Paradime needs the following permissions in each Jira project DinoAI will work in:

* **Browse Projects**
* **Create Issues**
* **Edit Issues**
* **Transition Issues**
* **Assign Issues**
* **Add Comments**

<Warning>
  **Use a classic API token. Scoped tokens are not supported.** When creating your token at [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens), choose **Create API token** and do **not** select any scopes (skip the "Create API token with scopes" flow).

  Scoped tokens only authenticate against Atlassian's API gateway, which the Paradime Jira integration does not use - connecting with a scoped token will fail with an authentication error.
</Warning>

<Check>
  **Tip:** Connect Jira with a dedicated service account whose project permissions cover exactly the actions above. Classic Atlassian API tokens and Data Center PATs are unscoped (they act as the user who created them), so the account's permissions are the real boundary of what DinoAI can do in Jira.
</Check>


## Related topics

- [Jira Cloud](/integrations/jira/jira-cloud.md)
- [Jira](/integrations/jira/index.md)
- [Power BI](/integrations/power-bi.md)
- [Jira Tool](/products/dino-ai/tools-and-features/jira-tool.md)
- [Jira Data Center](/integrations/jira/jira-data-center.md)