Issue Summary

When a Confluence Cloud page or space has view restrictions set to an Atlassian Team, members of that Team are able to access the content directly via its URL, confirming that permissions are correctly granting them view access.

However, those same pages are completely absent from Confluence search results, CQL queries, and any macro-based content aggregation that relies on search — such as Filter by Label and Page Properties Report. This inconsistency means that while the content exists and is technically accessible, it is effectively hidden from users' day-to-day workflows, as search is the primary way most users discover and navigate content.

The behavior appears to affect all pages where an Atlassian Team — rather than a traditional group — is used as the permission principal, and has been reproduced consistently across multiple search methods. Content restricted to standard groups is unaffected and returns normally in search results.

Steps to Reproduce

1. Navigate to a Confluence Cloud space and create or open a page

1. Set the page's view restriction to an Atlassian Team (e.g., "My Team")

1. As a member of that Team, confirm you can view the page directly via its URL

1. Use Confluence search (or CQL, Filter by Label, Page Properties Report) to search for content on that page

Expected Results

The restricted page appears in search results for users who are members of the Team, since the Team grants them view access.

Actual Results

The page does not appear in search results, CQL queries, or macro-based content lookups (Filter by Label, Page Properties Report) for Team members — even though those users can view the page directly.

The issue occurs because at search time, the user's Team membership is not resolved as part of their authorization principals, so the permission filter excludes the page from results.

Workaround

Use a regular group (not an Atlassian Team) as the permission entity on the affected pages. Pages restricted to a group appear in search results as expected.