Confluence Docs 3.0 : Guidelines For Partitioning Content Into Spaces & Pages This page last changed on Jun 17, 2007 by rosie@atlassian.com. Brief guidelines for grouping content into the Confluence space and page format used by Confluence. ### Partitioning Guidelines To ensure maintainable and logical spaces, content should be broken into spaces by: Evaluating permissions across the wiki content. If members require conflicting access, for example user 1 must access content on topics A and B, while user 2 must access content for topics B and C, then the topics must be separated into three spaces. Grouping content by topic, project or team. For semi-static content, a space for each topic is fine. If there is a substantial project-related content that must be exclusive to different groups, you should use separate spaces. ### Spaces & Pages Information Useful notes about spaces and pages: Spaces cannot be nested Page permissions can prevent users who can access the space from accessing that page Page permissions alone cannot keep the existence of a page secret. The page should be in a restricted space instead Pages can be easily moved between spaces

Document generated by Confluence on Nov 05, 2009 23:35