# Adding Jira organization to GitProtect

#### Adding Jira organization to GitProtect connects your environment to the platform so you can start protecting its data.

***

## Using an API token

{% hint style="danger" %}
For **Jira**, use the classic token — **GitProtect does not support scoped tokens**.
{% endhint %}

{% hint style="warning" %}
Before adding your **Jira** organization to **GitProtect**, [check if your account has the required permissions](/backup-and-recovery/jira/integration/required-permissions.md) for all spaces (projects) you want to protect.
{% endhint %}

{% stepper %}
{% step %}
Log in to **GitProtect Management Service**, open the **DevOps** tab on the left side of the window, and select **Jira** from the list.

<figure><img src="/files/bYvhS5COubawW4888AF9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click the **Connect** button under **Jira Software** or **Jira Service Management** (depending on your needs).

<figure><img src="/files/XFNs2P9DzhTQAd0Wx3lT" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Enter your **instance URL** (for example, <kbd><https://mycompanyjira.atlassian.net></kbd>) and your **Jira** login, then add or select an [API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token) from the **Password Manager**.

{% hint style="success" %}
**GitProtect** can secure organizations that have a custom domain added, but you must add the instance using its original URL, which you can find in <https://admin.atlassian.com> > **App URLs** > **Custom domains** > **Actions** > **Show details**. Learn more about custom domains in [this article](/backup-and-recovery/jira/integration/custom-domains.md).
{% endhint %}

<figure><img src="/files/TWa37Vq6kO6TxGJsiq6D" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Configure your spaces sync and default worker — specify hours for synchronization, or set a time interval for automatic updates. Once done, click **Proceed**.

{% hint style="warning" %}
The account used for the authorization process must have **at least site admin permissions**.
{% endhint %}

<figure><img src="/files/j44kVrfxNcZXQN2IkSYw" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Your **Jira** organization has now been successfully added to **GitProtect** — click **Custom policy** to adjust your backup policy settings, or click **Run backup** to execute the backup immediately using the current policy configuration.

{% hint style="info" %}
Granular backup is the default policy configuration applied to any new **Jira** organization you add to **GitProtect**.
{% endhint %}

<figure><img src="/files/GEREGP48GNs9UJfewuoz" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***

## Useful links and items

{% content-ref url="/pages/UqZB5pnMCMIjkZ8bOASb" %}
[Required permissions](/backup-and-recovery/jira/integration/required-permissions.md)
{% endcontent-ref %}

{% embed url="<https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/>" %}


---

# Agent Instructions: 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:

```
GET https://helpcenter.gitprotect.io/backup-and-recovery/jira/integration/adding-jira-organization-to-gitprotect.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.