Skip to main content

​
Overview

nOps uses an unscoped Atlassian organization Admin API key (plus an API key name and optional expiration date) to track usage and user activity in Inform. The key is stored securely, validated before save, and is not shown again after you connect.

​
Prerequisites

  • Organization Admin access in Atlassian (admin.atlassian.com)
  • Centralized User Management enabled (legacy user management is not supported)
  • Permission to create API keys without scopes
  • nOps organization administrator access
This integration requires Organization Admin permissions. Scoped API keys and limited admin roles will not work.
Only admins and owners can connect, re-validate, or disconnect in nOps. Members see Admin Only on connectable cards.

​
Create an Atlassian API key

  1. Sign in to Atlassian Administration with Organization Admin privileges.
  2. Go to Settings → API keys.
  3. Click Create API key.
  4. Enter a name (for example nOps Integration).
  5. Select API keys without scopes — required for organization Admin API endpoints (/admin/v1/orgs, user directories, and activity data).
  6. Set an expiration date (maximum one year) and create the key.
  7. Copy the API key immediately — it is typically shown only once.
See Atlassian Cloud Admin Scopes for why unscoped keys are required for these endpoints.

​
Connect in nOps

​
Where to open Atlassian

  • To connect for the first time — go to Settings → Integrations and click the Atlassian card.
  • To manage an existing connection — go to Settings → Account Status → Connected apps and click the Atlassian chip to re-validate or disconnect.

​
Connect steps

  1. Click the Atlassian card or chip.
  2. Enter API key name, paste the API key, and optionally set Expiration date.
  3. Click Connect.
nOps validates the key with the Atlassian Admin API before storing it.

​
Manage your connection

Administrators can Re-validate or Disconnect from the modal. Atlassian keys expire within one year — create a new key in Atlassian before expiry and connect again, or update after rotation.

​
Troubleshooting

  • Invalid key — confirm the key was created without scopes and your account has Organization Admin access.
  • No data — allow up to 24 hours; verify centralized user management and that users have activity in Jira, Confluence, or other Atlassian products.
  • Incomplete data — ensure the admin has access to all products you expect to track.

​
Security

Do not share the API key or store it in public repositories. Rotate before the expiration date you set in Atlassian or in nOps.

​
Reference