nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why am I unable to deactivate a user?

Kylie Lunghusen

I made an API request to the "Deactivate a user" endpoint. I got the "204 No Content" response that supposedly means it worked. But when I went into the admin console, the user was still only suspended and not deactivated.

I tried deactivating it manually, and the console said it had worked, but the account still appears as only suspended.

The account is a Managed account, which the docs say can be deactivated. The account is not provisioned from an identity provider, which according to the docs means I can deactivate it myself. (We use SSO to log in, but provisioning is via manual creation. And this user left years ago, so if IdP could deactivate it, it would have done so already.)

Any advice would be appreciated, thanks.

Accepted answers

Kylie Lunghusen

The issue seems to have resolved itself - the two accounts I tried this with are both now showing as deactivated when they were not before (I had refreshed the page, gone out and back in, waited a few minutes etc, and no change).

The delayed reaction is still an issue, as I've been asked to batch-deactivate a bunch of accounts and then report the new figures. I guess I'll just have to deactivate a couple more test accounts and then keep checking every 10 minutes or so in order to get an idea of how long the change takes to show up in the console.

Thanks for your help.

All comments

Martin Runge

Hi @Kylie Lunghusen

I would check where you are reading the status. The Users page and the Managed accounts page report two different things. Deactivating an account at the org level sets the managed account to Deactivated, while the site-level Users list keeps showing the person as Suspended because that is how it labels someone with no product access. So a 204 plus "suspended" in the user list is the expected end state.

I would confirm it here: admin.atlassian.com > Directory > Managed accounts > open the account and look at Account status. If it says Deactivated there, you are done, and the person cannot log in.

Two things I would also look at if Managed accounts still shows the account as active:

The user may have a role like billing admin and is blocked for deactivation for those reasons.
The email domain may have moved to another org that now claims the account

Cheers, Martin

Arkadiusz Wroblewski

Hello and Welcome to Atlassian Community @Kylie Lunghusen

Atlassian distinguishes between organization access status and managed account lifecycle status.

A user can appear as Suspended under Directory > Users, but their managed account itself may already be Deactivated. Take a look at the user profile directly via admin.atlassian.com > Directory > Users (filtered by Account type = Managed accounts), if it shows Deactivated, the operation succeeded.

Also a 204 No Content API response also confirms a successful lifecycle disable call.

Best,

Arek🤠

Kylie Lunghusen

Thanks for your help.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

confluence-cloud

atlassian-cloud