Content not visible in a private space even though I am an Admin of this space

Question

After a User got a new mail-address she didn´t have access to her private space anymore.
I invited her again to our Confluence and she can see the other spaces.

For her private space I went to the security setting and gave myself Admin-permissions.

After that, I gave her the admin permissions back. But neither her nor me can see the content in the Space. When I go to the "Content Manager" of the space it says "Someting went wrong, try again later"

I don´t see trashed or archived pages in this space.

The only weired thing is, that I get the "restricted content" message, when I go to the Space, but my coworker and I are admin of this space.

Any ideas, how I can recover the content of the space? We have the Standard Plan

Thanks

Tomislav Tobijas · Answer

I think I've seen this on one occasion, but I believe it was a backend issue that had to be resolved by the official Support team.

You could check with other admins if they can, once you give them space admin permissions, access "Content Manager" > if not, it's probably a problem that needs to be resolved on the Atlassian end. 👀

Barbara Szczesniak · Answer

@Marvin Arnst Did you modify the user's Confluence account to have a different email address or give the user a new account with their new email address?

You say that you invited her again, which makes me think that you created a new account. In this case, Confluence will not recognize her as the same user, so she won't own that personal space.

If you deactivated the old account, you might try updating it with the new email address and see if this works.

Staffan Redelius · Answer

Hi @Marvin Arnst and welcome

If you claimed permission via the security settings you should be able to access the space. If the page is restricted (via the padlock) it might be that nor you or the creator can access the page.

Since you are on standard you won't be able to bypass the restrictions (it is possible on Premium and Enterprise via using a "admin key"

I would suggest you to contact Atlassian support for this since it might be that you are not able to resolve it yourself.

Atlassian Support

Best regards,
/Staffan