Confluence Forge apps are affected by page-level permissions, even when the app has been granted the necessary scopes by an admin. 

• A user can restrict access to a page or its subpages, and unless the Forge app user is explicitly granted access, the app is entirely blocked from interacting with that content.

• The app’s functionality becomes limited or unusable, despite having been installed and authorized by an admin.

• Scopes alone are not sufficient to guarantee access if the user restricts the content, which undermines app reliability and consistency across user environments.

This limitation can create confusion for app developers and customers, as app behavior becomes unpredictable depending on how users manage their permissions. It also raises questions about the role of scopes versus user-controlled permissions.

Suggestion / Feature Request:

We propose a revision or enhancement to how Forge apps interact with restricted content, including:

1. A mechanism to allow apps (once installed and approved by admins) to access all content within a space or instance, regardless of user-imposed page restrictions.

1. Improved documentation and guidance for developers about this limitation.

1. A dedicated scope or flag to designate "admin-granted persistent access" for Forge apps, even on restricted pages.

This would help ensure that app behavior is consistent and aligned with the permissions granted at install time, reducing friction for both developers and users.

Impact:

• Enhances reliability and predictability of Forge apps.

• Aligns with expectations set by the scope-granting model.