space root/
　 ├ A contents/
　 ├ B contents/
　 │　 └ D contents/
　 └ C contents/

Summary

Currently, guest users in Confluence Cloud can only be invited at the space level. Customers cannot limit guest user access to a specific page hierarchy within a space (e.g., only “D contents” and its child pages), while hiding other content in the same space.

Description

A customer scenario highlighted the need to share only part of a space with external collaborators. For example, they created a space for internal documentation of a project but later needed to outsource part of the work. They wanted to grant guest access only to one sub-hierarchy (e.g., “D contents” and below) without exposing other sections of the space (“A contents,” “B contents,” “C contents”).

At present, this cannot be achieved because:

• Guest access is granted on a space-wide basis.
• Page restrictions inherit from parent to child, so it is not possible to restrict only part of the hierarchy while keeping other parts hidden.
• Workarounds (such as creating a new space or exporting content to HTML/Word) are inconvenient, error-prone, and degrade usability.

Suggested features

Introduce the ability for admins to:

• Invite guest users to a space but restrict their access to a specific page or hierarchy of pages.
• Manage guest visibility so that only designated sections of a space are exposed to external collaborators.
• Apply granular permission settings to guest users without requiring a full new space or complex page-by-page restrictions.

Expected outcome

Admins will be able to grant external collaborators access to only the relevant section of a space, ensuring:

• Reduced operational overhead and risk of misconfigured page restrictions.
• Improved security by preventing accidental disclosure of unrelated content.
• A smoother collaboration experience without needing to duplicate or export content into separate spaces.