> For the complete documentation index, see [llms.txt](https://docs.licensemeter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensemeter.com/connectors/atlassian.md).
# Atlassian
Find Jira and Confluence seats that outlived their users. One organization API key, read-only.
Atlassian product access survives offboarding more often than most. LicenseMeter reads managed users and their product access through the organization admin API and cross-checks each seat against Entra ID.
Open **Connectors > Atlassian** in your workspace.
LicenseMeter sample workspace. All names, costs and findings shown are demonstration data.
{% hint style="info" %}
The screenshot shows sample data, not a live connection or provider consent screen. In your own workspace, the page presents the appropriate connection or import controls.
{% endhint %}
## Setup
{% stepper %}
{% step %}
### Create an organization API key
In Atlassian Administration (admin.atlassian.com) under Organization settings > API keys, create a key. Only users with the organization admin role can do this. If the key offers API scopes, include read:accounts:admin (or create it without scopes). The connector reads managed accounts, so your organization needs at least one verified domain; unverified accounts are not returned.
[Atlassian organization admin API documentation](https://support.atlassian.com/organization-administration/docs/manage-an-organization-with-the-admin-apis/)
{% endstep %}
{% step %}
### Note the organization ID
It is part of the Atlassian Administration URL (admin.atlassian.com/o/) and shown alongside the API key.
{% endstep %}
{% step %}
### Connect
Paste the organization ID and the API key on the Atlassian connector page. Validated before storage, encrypted at rest.
{% endstep %}
{% endstepper %}
## Data used
* Managed users: email, name and account status
* Product access per user (Jira, Confluence) and last activity where Atlassian reports it
## Outside this connector's scope
* Issues, pages, projects or any content inside the products
## Findings and limitations
* Jira and Confluence seats held by accounts that are disabled in Entra ID.
* Seats with no matching directory account at all.
* Seats with no product activity for your inactivity threshold, where Atlassian reports it.
Managed-account coverage depends on verified domains. A successful connection with a partial user list should be investigated before treating absent users as offboarded.
After setup, check the refresh timestamp and [set contract prices](/licenses-and-prices.md) for any seat-based products. If validation or sync fails, start with [Troubleshooting](/troubleshooting.md).
---
# 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.licensemeter.com/connectors/atlassian.md?ask=&goal=
```
`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.
