User License Cleanup & Dashboard for Bitbucket

Find inactive Bitbucket users, see exactly why each seat is billable, and clean up without breaking your CI/CD pipelines.

Bitbucket Coming soon
Coming soon to the Marketplace How to use

Overview

User License Cleanup shows every inactive or never-logged-in user in your Bitbucket workspace, along with the exact access that keeps each seat billable.

It’s built to protect your pipelines: accounts that look like CI or automation are held for review, recent push activity blocks clean-up, and every change can be restored.

Features

Billable access breakdown

See which repository, project or workspace access keeps each seat billable.

Pipeline-safe detection

Accounts that look like CI or bots are held for review, and recent pushes or pull requests block clean-up.

Safe mode preview

See the exact plan before anything changes, including what was skipped and why.

One-click restore

Every removed permission is recorded, so all applied changes can be restored exactly.

Exclusion rules

Protect specific users or name patterns from ever being changed.

Dashboard and reports

Cost impact, inactivity trends, scheduled scans and CSV export.

How to use

Dashboard

Workspace settings → Forge Apps → User License Cleanup

API key

The Settings tab. Create the key at admin.atlassian.com → Settings → API keys

Exclusions

The Excluded tab

Plans and restore

The Cleanup tab

  1. Create an organization API key

    At admin.atlassian.com → Settings → API keys, create a key and copy it. It’s only shown once.

  2. Add the key

    On the Settings tab, paste the key and click Verify and save.

  3. Exclude CI and bot accounts

    On the Excluded tab, add every build, bot and integration account you know about.

  4. Run a scan

    Click Run scan now, then review the Overview tab.

  5. Preview in Safe mode

    On the Cleanup tab, review the plan and the Skipped by safety rails list below it.

  6. Apply, and restore if needed

    Switch to Live and confirm. If a build starts failing, click Restore all applied changes.

Good to know

  • Push and pull-request activity is tracked from installation onwards, so wait a few weeks before your first clean-up.
  • Keep the recent-activity safety window at 30 days or more.
  • Apps can’t change group or workspace memberships. The app tells you where to change them in Atlassian admin.
  • Optional notifications can be sent to Slack or Microsoft Teams.

Privacy

  • Reads last-active dates from Atlassian’s Organization API, using the key you provide.
  • Records only the date of each user’s latest push or pull request, never code or pull request contents.
  • The API key is kept in Forge’s encrypted secret storage and is never shown back.
  • Optional Slack or Microsoft Teams notifications are sent only to a webhook an administrator sets up.

Our privacy policy covers every AryonForge app.

What the first version includes

  • Inactive and never-logged-in user detection, with a billable access breakdown.
  • Pipeline-safe service account detection using push and pull-request activity.
  • Safe and Live modes, exclusion rules and one-click restore.
  • Dashboard, scheduled scans, audit log and CSV export.

Questions about User License Cleanup & Dashboard for Bitbucket?

Open a request in our support portal or email support@aryonforge.com. We reply within one business day, Monday to Friday.