Why do we see the Improved user management experience on some sites but not all?

[Antoine _Klee Group_]

Hi, this is something I still have not figured out.

In the user managment of some Atlassian sites, we sometimes see this view

and sometimes this one.

 

The first one allows us to remove site access but not the second one.

I am an org admin of both organisations and accounts are managed in both as well.

Also what is the clear difference between "Suspending access" and "site access removal" as well as suspended accounts and deactivated accounts?

Thanks.

[Kieren · Accepted solution]

Why do we see the Improved user management experience on some sites but not all?

Hi Antoine,

The improved user management experience is still slowly being rolled out to all our customers. Some orgs will take longer to migrate than others sorry. If you want to raise a support ticket asking for one of your orgs to be migrated to the new experience, we can take a look at what the delay is and work with you to speed that up.

one allows us to remove site access but not the second one.

Remove user exists on both experiences. Both will remove the user from your user list, i.e. they're totally removed from your site/org/products.

The 'Has access on site' toggle will suspend and unsuspend a user to your site. The 'Suspend access' button in the new experience does the same thing, only across your entire org and all products, not just a single site.

what is the clear difference between "Suspending access" and "site access removal" 

Suspending access for a user simply turns off the ability for that user to access any content in your products. It can easily be turned on again and the user will have access to everything they had before. This is helpful if someone is going on leave for a long time and your don't want to pay for their user while they're away.

Remove user will remove them from your site/org/products. You need to re-invite the user, add them back into all their previous groups, grant them previous project/space permissions, etc... to give them the same access they once had. Usually customers only use this feature when a user has left their company.

as well as suspended accounts and deactivated accounts?

Deactivated accounts are accounts that your Org has claimed (i.e. Managed Accounts) where that account has be deactivated by an Org admin. A user with a deactivated account cannot login into that account for any site or product. It's unusable.

A suspended account is only suspended in that particular site or org. The user can still access other sites/orgs that you may not know about, or use it in Trello or on community.atlassian.com.

[Antoine _Klee Group_]

Thanks @Kieren,

The 'Has access on site' toggle will suspend and unsuspend a user to your site. The 'Suspend access' button in the new experience does the same thing, only across your entire org and all products, not just a single site.

Therefore is there a way to suspend access to one site only with the new UI? I found this option quite convenient.

Thanks. 

[Antoine _Klee Group_]

Also @Kieren since you provided a very clear answer: I am looking for a way to automatise user deactivation (i.e. removing them their site access) but found no api endpoint to do so. It is possible to deactivate an account but as you fairly stated, this will also unable them to use personnal/pro trello or Atlassian comunity which is not what I want to do.

Is there a way to remove a user from accessing a specific site via API or is my only option to built a custom javascript that would "manually" click the "has site access" toggle?

Note that I wish to keep group membership history that's why removing the user from product access groups is not a proper option (since groups other than default ones also give product access on my site).

Thanks.

[Kieren]

is there a way to suspend access to one site only with the new UI?

No sorry.

Is there a way to remove a user from accessing a specific site via API

Not today sorry. But we do have a team working on this specific API (and a few others). You can track it here. Only option right now would be a custom script as you've described to manually click the toggle.

[Antoine _Klee Group_]

Thanks for your reply