Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Will "Revoke site access" do what I need it to here?


I'm new to my organization and Atlassian, so thanks in advance for any help! Some details are below:

  • I have a user who has two accounts, same name, under two different emails in our domain. They've requested that we modify/adjust the older account due to the confusion and mix-ups that are happening between the two accounts.
  • Both accounts have access to Confluence, but they are reasonably certain the older account does not have content/data associated with it.
  • I am a site admin of our Confluence Cloud instance, but not an org admin.

I saw that merging accounts is not an option, so am looking into how to close out the old account (though my preference is not to delete the account). I'm seeing resources on revoking site access, revoking product access, deactivating accounts - I am wondering what the differences between all of these options are (and there might be other options, too), and what would be the best to do in this scenario. Because I'm not an org admin I know I can't deactivate the account, and was wondering if the "Revoke site access" option (shown here) is suitable.Screen Shot 2021-01-13 at 7.28.21 PM.png

1 answer

0 votes

Hi and welcome to the community!

A quick search on other Q&A's, I found this link. Does this answer your question or do you need more breakdown?

Thanks for sharing that, Stephen (and for the welcome)! I saw that this compares the deactivation process to revoking application access, but doesn't mention what revoking site access does, which is the other option I was wondering about. Do you have any information on site access revocation?

Daniel Ebers Community Leader Jan 15, 2021

With product access you can control which products the user should have access to. Given the example you are using Jira and Confluence in your site - User A could have access to Jira, User B to Confluence, User C to both.
By revoking site access the user will not be able anymore to use the complete site (think of Jira + Confluence).
Other than removing a user from a site: the user will be removed permanently (this time they also do not count against the bill as for licensed users).

Thanks for walking through this, Daniel! Once site access is revoked for a user, what happens to content they've created or places they are tagged? Can you still see their old account name or is that no longer the case? I'm assuming they can no longer be tagged in new pages.

Daniel Ebers Community Leader Jan 18, 2021

The content should stay like it is but tagging (mention) is not possible anymore as far as I know - but please double check.

@Daniel Ebers We still can tag(mention) ex-staff. It so confuse when some users have same name with ex-staffs in my org. I requested a solution how can we control this but no Atlassian doesn't have that function :((

Daniel Ebers Community Leader Jul 25, 2021

Seeing a closed Suggestion ( this should work since a long time now - probably you could check if they are indeed inactive.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Confluence

Confluence Mythbusters: Does Atlassian even use Confluence?

Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...

1,611 views 7 30
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you