You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I signed up for a free Cloud account as a small documentation space for my own personal development projects. As a former Confluence Support Engineer, I was also curious about how the user management features work in the free version!
I found an interesting issue and thought I'd share it in case other users also encounter it. I tried to log this as a Feature Request at jira.atlassian.com but was routed over here.
When you create a Confluence instance, you must create your first space to populate the schema (or at least, this is how it is in the Server versions).
I created my first space in as part of the setup process and later realized that I wanted to change the content of that first space. I went back to the first space's content tools and found I had no rights to delete the space:
I believe this relates to how the administrator rights work in the free version of the app. I'm not sure if this is intentional behavior, but it would be nice to be able to delete the first created space. Oftentimes users aren't thinking so much about the content of their new sites, but rather its setup when they are prompted to create the space. It's quite easy to misname a space in the wrong context and then want to delete it to clean up the site.
The original bug has been resolved for any new Confluence Cloud Free sites, however another fix will need to be applied for any existing sites with this issue.
If you created your Confluence Cloud Free site before Jan, 8th, 2020, you will still be impacted by the bug.
If your site is affected, you can follow the progress of the fix in this new bug ticket: