> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.46.6/built-in-connectors/atlassian-cloud.md).

# Atlassian Cloud

The Atlassian Cloud connector for Elimity Insights fetches users and groups from your Atlassian Cloud tenant so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Generating an API key in Atlassian Cloud

This connector uses an API key to authenticate with Atlassian Cloud. Please refer to [the official documentation](https://support.atlassian.com/organization-administration/docs/manage-an-organization-with-the-admin-apis) for detailed instructions on how to generate such a key. Make sure you create an API key without scopes; Atlassian does not yet support a scope with read-only access to users and groups. Note down your organization ID and the generated key for use in the next step.

## 2. Creating a source in Elimity Insights

In Elimity Insights you can now create a new Atlassian Cloud source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>Organization ID</td><td>The unique identifier of your Atlassian Cloud organization which you noted down in step 1.</td></tr><tr><td>API key</td><td>The key you generated in step 1.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.elimity.com/reference-manual/v3.46.6/built-in-connectors/atlassian-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.