Documentation

Check the installed build before following these steps.

• Install or open Confluence Exposure Monitor in the authorized Confluence Cloud site
• Confirm the necessary administrative permissions and app access
• Open the dashboard and initiate or inspect a supported scan
• Review findings, timestamps and coverage or authorization notices
• Verify the reported access state in Confluence before changing anything

Findings are review leads, not proof of a data breach.

• A potential exposure finding is not proof that an unauthenticated person viewed a page
• Missing findings do not demonstrate the absence of exposure
• Visibility can depend on app permissions, restrictions, API limits and scan coverage
• Keep evidence and authorization observations with the review record where supported

Production-specific details must come from the actual build.

• Match OAuth scopes to the released Forge manifest
• Check which Confluence spaces, pages and metadata the scanner reads
• Confirm whether any audit data is retained and for how long
• Do not assume automatic permission changes or full tenant coverage

Validate inputs and access first.

• Check the installed app version and account role
• Check space/page restrictions and site authorization
• Inspect scan status and quota or permission errors
• Retry with a documented example and contact support using redacted data