> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-saas-security/saas-ai-agent-security/onboard-saas-ai-agents/onboard-atlassian-rovo.md).

# Onboard Atlassian Rovo

To access your Atlassian instance, AISPM requires the following information, which you will specify during the onboarding process.

| Admin Email     | <p>The login email address of the Atlassian Org Admin who created the API token and API key.</p><p><br></p>                                                                                                                                                                                                                                                                                        |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API Token       | A token, generated by an Atlassian Org Admin, enables SSPM to authenticate to the administrator account.                                                                                                                                                                                                                                                                                           |
| API Key         | A key, generated by an Atlassian Org Admin, that enables SSPM to scan and update organization settings and user accounts. SSPM uses this key to identify and manage the third-party plugins that users have connected to Jira or Confluence.                                                                                                                                                       |
| Organization ID | A unique, automatically generated identifier for your Atlassian Cloud account, serving as the primary identifier for managing users, products, billing, and settings centrally within the Atlassian ecosystem. Unlike organization names, which aren't unique, the Organization ID guarantees each organization has its own distinct identifier for use in the URL, API, and various integrations. |

1. Generate and Copy an Administrator API Token.
   1. Log in to Atlassian using Org Admin credentials.
   2. From the Atlassian account profile, navigate to the API tokens page for the account (select Security > Create and manage API tokens or go to [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens)).
   3. Click Create API Token.
   4. Specify a name and an expiry date for your API token and click Create.
   5. Copy the generated API token. Do not continue to the next step unless you have copied it, as you must provide this token during the onboarding process.
2. Generate and Copy an API Key and an Organization ID.
   1. Log in to the [Atlassian Admin Portal](http://admin.atlassian.com/) (admin.atlassian.com) using Org Admin credentials.
   2. If you administer more than one Atlassian organization, select the organization you want SSPM to scan.
   3. Select Organization settings > API keys.
   4. Click Create API key.
   5. In the "Before you begin" page, choose "API key without scopes" and click Next.
   6. Specify a name and an expiry date for the key and click Next.
   7. Review your API Key details and click Create API key.
   8. Copy the Organization ID and the API key. Do not continue to the next step unless you have copied both, as you must provide this information during the onboarding process.
3. Onboard Atlassian Rovo Platform to Cortex.
   1. Log in to Cortex.&#x20;
   2. Select **Settings > Data Sources and Integrations > Add New**. You can use the Search bar to find the Atlassian connector.
   3. Click on the Atlassian tile and select the Add Another Instance.&#x20;
   4. On the **Capabilities** page, provide an Instance Name and select the Agent Security scanning capability.&#x20;
   5. Under **Connections**, provide **Admin Email** and **Organization ID** to authorize the connection. In addition, under **Agent Security Scanning**, provide the API Key and API Token to authenticate the application.
   6. Once Cortex validates the credentials and permissions, the onboarding process is complete.
4. **Validation and Scanning**: Cortex will immediately begin scanning your onboarded platform. Note that scan time varies based on the amount of data; it takes at least one hour to display data in the AISPM dashboard.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-saas-security/saas-ai-agent-security/onboard-saas-ai-agents/onboard-atlassian-rovo.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.