> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/atlassian-credentials.md).

# Atlassian: Credentials

### Overview

BalkanID supports discovery and governance of credentials within Atlassian (Jira and Confluence) as part of **IGA for Non-Human Identities (NHI)**. Because Jira and Confluence share a centralized identity architecture, user directory, and global groups at the organization plane, this common application unifies both environments.

All credentials are normalized into the BalkanID data model and surfaced in the Credentials tab, along with their associated identities, access relationships, and risk insights.

The associated credentials can also be seen under the specific application integration (Atlassian) page.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FnEcVdyLn06r8raJJMuq9%2Fimage.png?alt=media&amp;token=4346eed4-04f5-4eae-ab81-5f2c6414751f" alt=""><figcaption></figcaption></figure>

### Required Atlassian Scopes for Credential Discovery

To enable full credential discovery, please refer to the [Service Account API Scopes](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/atlassian-application-integration-setup.md#create-api-token) and the [Organization API Token scopes](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/atlassian-application-integration-setup.md#get-your-organization-admin-token) sections in the [Atlassian Integration Setup](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/atlassian-application-integration-setup.md) page

These APIs allow BalkanID to build a complete view of credential inventory, access, and usage.

### Credential Types Supported

BalkanID tracks the following Atlassian credential types:

{% hint style="info" %}
Note: The credential types listed below are examples and do not represent the full set of supported Atlassian credentials.
{% endhint %}

* Atlassian API Tokens (Personal): Long-lived tokens generated by individual organization-managed users to script or query Jira and Confluence REST APIs without exposing passwords.
* Org API Keys: Highly privileged organization-scoped keys managed at the administration console level to query directory settings, audit logs, and user provisioning.
* Service Account Tokens: Highly persistent API tokens assigned to explicit non-human/bot identities to run automated pipelines, sync applications, or third-party integrations.

### Common risks associated with Atlassian credentials include:

* Stale and Dormant Access: Personal API tokens, Org API keys, or Service Account tokens left active despite being completely unused for 90+ days.
* Unmonitored Orphaned Credentials: Active tokens created but never once utilized, creating clean, untracked attack vectors.
* Imminent Credential Expiration: Critical service account or personal tokens set to expire within 30 days, creating a potential vector for sudden operational downtime.
* Elevated Cross-Product Blast Radius: Over-privileged Service Accounts or Org keys that accidentally expose access bridges across both Jira projects and Confluence spaces due to shared global group memberships.

This ensures visibility and governance of programmatic access in Atlassian, forming a critical part of IGA for Non-Human Identities.


---

# 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.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/atlassian-credentials.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.