Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cannot delete the first created space in a Confluence Cloud account (Free subscription)

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 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: 

Screen Shot 2019-12-08 at 11.50.45 AM.png



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. 

2 answers

1 accepted

1 vote
Answer accepted
Kat Marketplace Partner Dec 08, 2019

@Kat Thanks so much! This is exactly what I was looking for. :) 

My +1 for this too. Thanks


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: 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events