In Confluence Cloud, a classification level labels content; it does not by itself restrict who can view a page. To limit visibility, apply a page content restriction and choose permitted users or groups. The page’s audience is still bounded by access to its space and any restricted parent page.
Classification and page restrictions do different jobs
Use classification to describe the sensitivity or category of content and, where configured, inform separate policy controls. Use content restrictions to control who can view or edit a particular page. A classification badge alone is not documented as a viewer restriction. See Atlassian’s overview of data classification and its guide to restricting Confluence content.
| Control | What it does | Scope | Who configures it |
|---|---|---|---|
| Space permissions or roles | Determines who can access content in a space | Space | Space admins |
| Content restrictions | Narrows who can view or edit an individual item | Page or other content item | People with the required edit and restriction-management permissions |
| Classification level | Labels content and can inform separate policy controls | Organization, space, or individual object | Organization admins configure levels and settings; permitted users can classify content |
| Classification rule | Applies a level when a configured detection matches | Matching content objects; may include existing content | Organization admins |
Restrict a page to its intended audience
- Check the space first. Confirm the intended readers can access the page’s space. A page restriction cannot grant access to someone who lacks access to the containing space or a restricted parent.
- Open the page’s restriction controls. In Confluence Cloud, open the page and use its content-restriction or page-restriction control. The exact role and permission experience can vary as Atlassian rolls out role-based access, so check your site’s current interface.
- Set viewing access. Choose the option to restrict viewing, then add the users or groups who should be able to view the page. Add edit access separately if only some viewers should be able to change it.
- Save and verify. Confirm the restriction is in effect and check access through groups as well as direct user assignments. Confluence permissions are additive: another group or access source can still give a person access.
Confluence content is generally available to people who can access its space or parent unless it is restricted. Content restrictions are not customizable on the Free plan. Atlassian’s content restriction documentation describes the control and its permission requirements.
Configure classification separately
Data classification for Confluence Cloud is documented as an Atlassian Guard Premium capability; Atlassian also lists availability for Atlassian Government Cloud. An organization admin defines classification levels and publishes them before users can apply them. Atlassian documents support for up to 10 levels. Check the current entitlement and configuration options for your tenant in Atlassian’s setup guide and classification-level guidance.
#1 Best Overall
Set defaults with scope in mind
Organization defaults provide a baseline for new or unclassified content. A space can have its own default, and administrators configure whether that default may be less sensitive than the organization default. A classification assigned to one page applies to that page, not automatically to its child pages. Classification scope and page-access inheritance are separate behaviors; review both when organizing a hierarchy. See Atlassian’s classification settings guidance.
Control who can classify content
Manual classification permissions are configurable. The documented default is anyone with edit access; administrators can instead limit manual classification to space admins or prevent manual classification. Set the permission policy to match your governance process rather than assuming that page editors can or cannot classify content. Details are in Atlassian’s settings documentation.
Review automated rules before applying them
Classification rules can apply levels when configured detections match, and rules may affect existing content. Before saving a rule, inspect its preview and its settings for updating existing content. Atlassian identifies classification rules as early access in some support documentation, and administration experiences can differ; confirm the feature’s current availability and behavior in your site. See the rule setup guide.
Quick Recap
Best Value
Rank #3
- Used Book in Good Condition
Check the access model before relying on a restriction
- Make sure the permitted readers have access to the page’s space and any restricted ancestor.
- Review every group that grants access, not only the person’s direct assignments.
- Check child pages individually: a parent’s classification does not classify its children, and a page’s restriction does not replace a review of the child’s own access.
- Verify which users may manage restrictions and classifications under your site’s current roles and permissions.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
