The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Audit Confluence by comparing each space’s and content area’s intended classification with the access people actually receive through global, space, content, group, and anonymous-access settings. A classification label or default does not, by itself, restrict access: Atlassian documents classification defaults separately from its permission controls.
Confirm what classification controls are available in your Confluence tenant
Atlassian’s classification-controls guidance describes the feature as part of an early access program, so the experience and menus may vary. The guide lists Atlassian Guard Premium for Confluence Cloud and says the feature is available in Atlassian Government Cloud. Confirm availability and entitlement in your tenant before relying on particular controls.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Atlassian Confluence 5 Essentials | $21.74 | Buy on Amazon |
| 2 |
|
Finance Record Book for Small Churches | $12.82 | Buy on Amazon |
| 3 |
|
The New Real Book | $47.00 | Buy on Amazon |
| 4 |
|
Latin Real Book: C Edition | $38.99 | Buy on Amazon |
| 5 |
|
Trading with Confluence: A Risk-Based Approach to Trading Equity Index Futures | $22.89 | Buy on Amazon |
The documented controls include whether space administrators may set a default classification to any sensitivity or only to a more sensitive level. Atlassian also directs administrators to ensure spaces have the intended default classification. These settings help establish classification; they do not replace permission checks.
Set the audit scope and policy baseline
Start with the organization’s own classification policy. Atlassian’s documentation explains how to configure defaults, but it does not define what each organization’s classification levels should mean or which audiences each level permits.
Recommended Free Tools
#1 Best Overall
- List the classification levels and the intended audiences or access conditions for each.
- Identify the spaces and, where relevant, pages or other content areas that should carry each level.
- Record the configured classification or space default alongside the policy expectation. Flag spaces whose default is missing or does not match the intended use.
Keep this baseline distinct from the access inventory: it says who should have access, not who currently has it.
Review effective access in Confluence Cloud
Atlassian describes three permission layers: global permissions, space permissions, and content restrictions. Space permissions control which users or groups can view, add, edit, or delete content in a space; content restrictions can further limit viewing or editing within it. Review all three layers for the spaces and content in scope.
Rank #2
- Enough forms for 1 year for churches of approximately 150 members
- 5 3/16" x 9"
- Includes forms for church receipts, member contributions, and disbursements
Inspect each user’s space-access sources
In Confluence Cloud’s role-based access experience, open Users in the space settings and search for a relevant user. Atlassian’s space-access troubleshooting guidance says this view shows direct individual access and applicable groups or user classes. Capture every displayed source and the access it grants, rather than recording only the user’s individual role. The exact experience may differ by tenant.
Follow group and user-class access
Confluence permissions are additive: access from multiple sources accumulates. A less permissive direct assignment does not cancel access granted through a more permissive group or user class. Check the membership behind each applicable group or class, and identify the source that grants any access beyond policy. To reduce access, change or remove the granting source; changing a different, less-permissive source will not neutralize it.
Rank #3
- Used Book in Good Condition
Check content and parent restrictions
Content is generally available to people who can access its space or parent unless restrictions narrow that audience. Atlassian says content can only be further restricted from its container, and view restrictions may be inherited by descendants. Review restrictions on the content itself and relevant ancestors, along with sensitive child pages. Record both viewing and editing access: a restriction for one does not establish the other.
Include anonymous or public exposure
Atlassian documents anonymous access as a possible site- or space-level exposure. Check whether it is enabled for any in-scope space or site, and determine whether that exposure conflicts with the classification policy. Do not infer that a classified label prevents anonymous access.
Rank #4
- Features Over 160 Latin Songs
- Arranged for C Instruments
- Standard Notation
- 48 Pages
Record the comparison and resolve mismatches
For each audited space or content area, keep a record that connects policy intent to the access evidence. A useful audit matrix is:
| Audit field | What to record |
|---|---|
| Scope and owner | Space or content area reviewed, plus the accountable owner. |
| Classification intent | Policy-required sensitivity and intended audience. |
| Configured classification | Applied classification or space default, and whether it matches the intended level. |
| Space access | Users, groups, or user classes; their access sources and effective roles. |
| Content restrictions | View and edit restrictions on the item and relevant parents, including inherited view restrictions. |
| Public exposure | Whether anonymous access applies and the affected scope. |
| Exceptions and action | Approved exceptions, identified mismatches, remediation owner, status, and recheck date. |
Prioritize mismatches that expose content to a broader audience than policy allows. For each one, identify the exact source of access, assign an owner to change that source or correct the classification/configuration, and verify the resulting access after the change. Retain the evidence and recheck date so the audit has a clear trail.
Best Value
- Used Book in Good Condition
Use audit logs as event history, not as the access inventory
Atlassian’s plan documentation says the Standard plan audit log can be used to review certain site events, including global permission changes. Use logs to understand relevant changes over time, but pair them with the current user-access sources, group memberships, content restrictions, and anonymous-access checks. The cited documentation does not establish that logs alone provide a complete snapshot of effective access.
Keep Data Center procedures separate from Cloud
For Confluence Data Center, Atlassian’s knowledge-base article documents SQL queries to list pages with view or edit restrictions and identify descendants inheriting view restrictions. It treats inherited view restrictions separately from edit restrictions. The article was updated July 30, 2026, and is explicitly for Data Center; do not apply its SQL method to Confluence Cloud.
Because the resulting inventory exposes permission information, handle query output as sensitive data and validate the query against the deployed Data Center version and internal change controls before running it.
Quick Recap
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.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
