Managing access in Confluence requires a clear distinction between space permissions and page restrictions, as they operate at different levels to control who can view or edit your content. Understanding the difference is essential for administrators who need to balance broad team collaboration with sensitive, confidential information. While both methods restrict user access, they apply their rules in unique scopes and contexts.
Defining Space-Level Permissions
Space permissions govern the overall visibility and interaction within an entire Confluence space, providing a foundational layer of security for large groups of pages. These settings are configured in the space tools menu and determine the default access for users and groups regarding that specific space. Administrators often use space permissions to create isolated environments for departments, projects, or client-specific work.
When you set a space permission, you are defining who can enter that space, add new pages, comment, or export the content. This is a proactive approach to security, as it prevents unauthorized users even from seeing the space exists in the global directory. For example, you might grant "Marketing Team" members "Add," "Edit," and "Comment" rights while removing "View" access for the general anonymous user.
Key Settings and Scope
The configuration interface for space permissions allows for straightforward management of user and group roles. You can assign specific global permissions, such as "Add Space" or "Create Personal Dashboard," or tailor restrictions specifically for that space. The scope is absolute; if a user lacks "View" permission for the space, every page within it is inherently inaccessible, regardless of individual page settings.
| Permission Level | Applies To | Use Case |
|---|---|---|
| Space Permissions | Entire Space | Department isolation, project confidentiality |
| Page Restrictions | Individual Page or Template | Sensitive drafts, targeted audience content |
Drilling Down to Page Restrictions
Page restrictions offer granular control within a space, allowing you to limit access to a single page or a specific blueprint template. Unlike space permissions, which act as a gatekeeper for the entire container, restrictions function as an override. You can keep a space generally open to a group while hiding a single sensitive page from everyone except a few individuals.
This functionality is particularly useful during the drafting phase of a document. A team might be collaborating openly in a space, but a specific page containing strategic financial data needs to be hidden from all but the executives. Page restrictions provide that temporary, targeted lockdown without disrupting the workflow of the rest of the space.
The Inheritance Hierarchy
It is critical to understand that page restrictions exist within the hierarchy of space permissions. A user must first have "View" permission for the space to even see the page menu. If they lack that, the page restriction is irrelevant because they cannot navigate to the page at all. However, if a space is public, a restriction applied to a page will successfully hide that specific content from the public while the rest of the space remains visible.
To manage these effectively, utilize the "Restrictions" tab found at the bottom of every page editor. Here, you can specify exactly which users or groups are denied access. This interface also clearly indicates if the restriction is inherited from a space-level setting or if it is a unique, custom rule applied directly to that page.
Strategic Implementation and Best Practices
To build a robust information architecture, you should view these tools as complementary rather than competitive. Relying solely on space permissions can lead to overly broad access, while leaning only on page restrictions creates a complex and difficult-to-manage maze of exceptions. The most efficient strategy involves planning your space structure around confidentiality levels.
- Use Space Permissions to define the general audience and team members who require access to a collection of related pages.
- Use Page Restrictions to handle exceptions, sensitive data, or content that is only relevant to a subset of the space members.
- Regularly audit both settings to ensure that user roles and project statuses are still aligned with the current access rules.
