Atlassian fixed FRGE‑212, enabling Forge apps’ system users to access restricted content via REST API calls when scopes are declared in the manifest, as documented in JAN 2022 “Forge apps can now access restricted resources” thread community.developer.atlassian.com+11community.developer.atlassian.com+11community.developer.atlassian.com+11.
However, this fix does not extend to Confluence event delivery. Specifically, page-viewed or page-updated events under avi:confluence:viewed:page or similar are still not delivered for restricted pages/spaces unless the app is manually granted view access.
Why This Matters
- Legacy parity loss: Connect apps historically received events for restricted content regardless of permissions. Forge has introduced limitations that break tracking functionality.
- Events still blocked: Even after FRGE‑212, event delivery remains restricted by Confluence’s permission model. The system user must be added to each restricted page or space manually.
- Use case: Page View Tracker: Our Forge app depends on complete event coverage across all pages. Without events for restricted pages, analytics are incomplete, and valuable usage data is lost.
I have created ECOHELP-73612 fro tracking the same
Requested Resolutions
Please enhance Forge’s event system so that:
- Page-View Events (and related) are delivered to Forge apps regardless of restriction settings, restoring parity with Connect;
- Or, provide a programmatic mechanism (e.g., manifest flag or events opt-in) to allow apps to subscribe to events for restricted content without manual permission assignment
Cheers
Ajay