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; } } }

Off boarding accounts

Gershon Chapman

What's the proper way of offboarding a user that's no longer a part of your org that will completely remove it from the Atlassian account and line of products? As of right now, my admin will delete the account from Bitbucket, and I'll revoke site access to the account from within Jira. I revoke site access because we'd still like to search and see the name records of tickets and confluence article of what that user did. What we've noticed is that when I pull the user up in Jira user management. The user not only still has access to BitBucket. But we're still being billed for the user's access to it even though they were deleted from it. Why is that??

Accepted answers

Kieren_63fgza

Hi Gershon,

Atlassian Access billing is applied to all users who you've completed a domain claim for and that use a product. That product doesn't need to be a product within your Organization, since the security settings are applied to every user you've claimed, regardless of who's product they are accessing.

My guess is that user X in your screenshots has access to another Bitbucket repo or workspace, which is why they're still getting billed via Atlassian Access.

This does not mean they have access to any of your content... From the steps you've described, you've correctly removed them from being able to access any of your content.

I would recommend Deactivating user X's account. They can then no longer use this account to access any content on any product, and you'll no longer be billed for them via Atlassian Access.

Cheers,

-Kieren

Atlassian Identity Product Manager

All comments

Kieren_63fgza

Hi Gershon,

My guess is that user X in your screenshots has access to another Bitbucket repo or workspace, which is why they're still getting billed via Atlassian Access.

This does not mean they have access to any of your content... From the steps you've described, you've correctly removed them from being able to access any of your content.

I would recommend Deactivating user X's account. They can then no longer use this account to access any content on any product, and you'll no longer be billed for them via Atlassian Access.

Cheers,

-Kieren

Atlassian Identity Product Manager

Gershon Chapman

I understand why the account would be billed via Access. But more importantly, is when I look at all of this. It seems like the user has to BB when I check Jira even though it was deleted from BB. Why would it still should up in Jira? It also looks like we're still being billed for BB account as well even though it was removed from there. Why isn't the account removed through the system and are we still being billed for it or not?

Kieren_63fgza

Hi Gershon,

I'd recommend opening a support ticket with Atlassian to help answer your last questions, I'm not sure I can help more without being able to see your site and settings.