Is there a limit to number of pages we can create in one space in Confluence Cloud?

[Krishna Vemulapalli]

Q1: Is there a limit to number of pages we can create in one space in Confluence Cloud?

Q2: can you please let us know the Pros and Cons of having one space architecture vs multiple spaces architecture in Confluence cloud?

Thank you!

Krishna

[Dave Mathijs]

Hi @Krishna Vemulapalli welcome to the Atlassian Community!

In addition to the earlier answers provided, have a look at this article from our partner K15t: How to structure Confluence content for long term success

[Barbara Szczesniak]

@Dave Mathijs Thank you for the link to this article.

I have so far been working in Free Cloud, documenting an application for my company. We will soon be moving to Standard and opening Confluence use to other team members.

Before this happens, we need to plan out how to approach wider use, since none of those other people should be creating any content in my space for the app documentation.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

There is a limit, technically, the database could run out of unique IDs for pages.  But that limit is so large, your authors will never reach it in their lifetime.

There are no pros to using a monolithic single space, you end up with a flat permissions structure (everyone works the same way across all your pages unless you spend lots of their time making them apply restrictions), you can only have one set of templates, one set of authors, one layout and look and feel, and one way of working.

Use spaces - you can structure them differently when they're for different purposes - you probably don't want the same structures for a Team documentation as you do for the Technical documentation for a produce, or your intranet, or or or...

[Benjamin]

Hi @Krishna Vemulapalli ,

There doesn't seem to be a set limit. I have work on spaces that have thousands of pages. However, it not great if there's thousand of pages if not all pages have any user engagement or not relevant to the current times.

Have everything is one space may lead to this monolithic structure and just dumping all documentation into one spot. Having multiple spaces allow to separate different documentation from each other. For example, if you have IT doc and HR doc, it's better to have an HR and an IT space, so when user is looking for certain docs, they know what space to go to. Also, this helps with ownership and maintenance. Rather than have owners maintain all the doc in a space. You can have an owner maintain the IT space and another for the HR space. 

Hope this helps.

[Krishna Vemulapalli]

Thank you  @Benjamin, @Dave Mathijs, @Nic Brough -Adaptavist- for the warm welcome and for sharing the information. It is greatly appreciated and truly helpful.