# How to Safely Bulk-Delete Multiple Users from Your Atlassian Cloud in 3 Steps

> A step-by-step guide to efficiently and safely removing multiple user accounts from your Atlassian Cloud, cutting license costs along the way.

Source: https://www.xalt.de/en/blog/user-cleanup-in-atlassian-cloud/

TEAM XALT Atlassian Platinum Partner · 18 June 2025 · 5 min

In fast-growing companies, outdated, duplicate or inactive user accounts quickly accumulate in the Atlassian Cloud. This affects not only test users or former employees, but also service accounts, temporary external parties or incompletely migrated accounts.

These can:

- **incur licence costs**
- **pose security risks** through forgotten access credentials
- **complicate administration**, especially during audits or reorganisations

Especially after migrations, reorganisations or in test environments, it makes sense to deliberately remove unused accounts. In this article, you will learn how to **efficiently and controllably delete multiple users from your Atlassian Cloud**.

## Typical use cases

This guide **assumes that your instance includes Jira Cloud and**is particularly suitable for:

- After a tested user migration, where the environment needs to be prepared for another run.
- Following a corporate merger or a systematic cleanup, where outdated accounts are to be removed.

**Important note:**If your users and groups are managed via Atlassian Guard with SCIM provisioning, this guide will not work. These accounts will simply be re-synchronised when your IdP is next updated.

Instead, contact your identity provider's administrator to manage SCIM-provisioned users directly through their IdP.

## Step-by-step guide: Removing multiple users from Atlassian Cloud

### Step 1: Check User Management Setup

- Go to admin.atlassian.com
- Select the appropriate organisation
- Navigate to the user overview

  - **If you are a Site Admin** via *Product site*
    - **If you are an Organisation Admin** via *Directory*

### Step 2: Prepare user data

- Go to admin.atlassian.com and select your organisation.
- Depending on your setup:

  - **Original view:** Select the site name/URL and then go to *Users*.
    - **Centralised view:** Go to *Directory \> Users*.
- Now export the user list:

  - **Original view:** Click *Export users*.
    - **Centralised view:** Click the menu at the top and select *Export users*.
- Choose which users you want to include:

  - *All users* - All users (active, suspended and deactivated) are included.
    - *Specific groups* - Includes only users in selected groups.
- Optional, but helpful:

  - *Group membership* - Shows which groups each user belongs to.
    - *Product access* - Shows which products and roles each user has.
- Click *Export users*. You will receive an email when the CSV file is ready. Check your spam folder if it takes a while.
- Open the email and download the file (you may be asked to sign in first).

### Step 3: Cleaning the data

Open the CSV file in Excel, Google Sheets or a text editor and:

- **Remove all users you do not want to delete**, e.g. organisation administrators.
- Remove your own **line** to avoid accidental lockout
- **Keep the *User id* column** - it is important for the deletion process.

Save the cleaned CSV file. Once it is ready and you send it to us, we will take care of the rest.

This is how you export the user list in your Atlassian Cloud as a CSV file for user cleanup.

## The benefits of user cleanup at a glance

A cleaned user list offers numerous benefits – from an IT as well as an economic and security perspective:

- **Reduce license costs:** Only active users need a license – this saves real money
- **Minimize security risks:** Old or forgotten accounts can represent potential attack surfaces
- **Better overview for IT admins:** Fewer users mean less complexity regarding roles, groups and permissions
- **Simplify compliance:** Clear data situation during audits or external reviews
- **Improve end user experience:** Fewer name conflicts, duplicates or outdated data
- **Faster onboarding:** New employees can be assigned to groups and projects more precisely

## Conclusion: Lean user lists = Secure & efficient Atlassian Cloud

The more users are created in your system, the more complex and risky the administration becomes. With a well-thought-out cleanup strategy, you create:

- **Transparency and control**
- **Cost savings through license optimization**
- **Security in the sense of Zero Trust and access restriction**
- **Maintainability for admins and IT teams**

Those who actively maintain their Atlassian Cloud will have fewer problems in the long run, more control – and save money in the process.

### For the technically inclined:

Do you want to dive deeper or use APIs yourself? These Atlassian guides explain how to work with Postman and REST endpoints:

[Delete groups from Atlassian Cloud](https://confluence.atlassian.com/cloudkb/delete-groups-from-atlassian-cloud-using-postman-and-rest-apis-1295679991.html)

[Bulk disable users from Atlassian Cloud](https://confluence.atlassian.com/cloudkb/bulk-disable-users-from-atlassian-cloud-using-postman-and-rest-apis-1388159392.html)

## We support you in the implementation and assist with

- User cleanup
- Automation with REST API
- License management & reporting

[Your contact at XALT](https://www.xalt.de/en/contact/)

![Foto von acht Personen des XALT-Teams, die die goldenen Buchstaben X, A, L und T hochhalten, eine Kollegin liegt davor auf dem Parkettboden](https://cdn.sanity.io/images/c475o02b/production/ba38c3afc15321082c8faacbaf2e7d540b9d7859-2560x1440.jpg?w=1504&q=75&fit=max&auto=format)

## Need to clean up users in your Atlassian Cloud?

We support you with user cleanup, REST API automation, and license management.

[Talk to us](https://www.xalt.de/en/contact/)

## More articles

### [Personal AI Agents Compared: Rovo, OpenClaw, and Agent SDKs Like Claude or OpenAI](https://www.xalt.de/en/blog/personal-ai-agents-compared-rovo-openclaw-and-agent-sdks/)

Rovo, OpenClaw, or Claude/OpenAI: how personal AI agents differ in 2026 and which approach fits your team.

*Atlassian*

### [BaFin Compliance for Atlassian Cloud – What Financial Institutions Need to Know Now](https://www.xalt.de/en/blog/bafin-compliance-atlassian-cloud-migration/)

New EU FSA rules have been in effect for Atlassian Cloud in financial services since December 2024. We show what has changed and how you can migrate to the cloud in a BaFin-compliant way.

*Atlassian*

### [Atlassian Team '26 Recap: The Shift to the AI-Native Organization and the Role of the Teamwork Graph](https://www.xalt.de/en/blog/atlassian-team-26-recap-teamwork-graph/)

XALT was on the ground at Atlassian Team '26 in Anaheim. Our recap covers the Teamwork Graph, Rovo, and the new Teamwork, Service, Product, Software, and Strategy Collections – and what it means for enterprises in Germany.

*Atlassian*

---

*This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*
