Integration · Knowledge + docs
On roadmap — not yet shippedClarityLift + Confluence
Confluence page-comment signals. Roadmap — not yet shipped. Page body content is out of scope.
Signals derived from Confluence
Team friction (page-comment tone)
Communication health (review participation)
OAuth scopes ClarityLift requests
Every scope below has a documented purpose tied to a specific step in the data flow. ClarityLift never requests scopes it does not use.
read:confluence-content.summary
Page metadata
read:confluence-content.comment
Comment content
read:confluence-user
Resolve users for the consent gate
Data flow, end to end
- 1Site admin installs the ClarityLift Confluence app.
- 2Admin selects which spaces to connect.
- 3Confluence delivers comment events via webhook.
- 4Aggregate signals derived from comment threads.
What ClarityLift does NOT read on Confluence
The privacy posture is led by what is excluded, not what is included.
- Direct messages between individuals — never read, ever.
- Group DMs — out of scope by design.
- Channel content from teams below the 10-member group floor.
- Personal account content of any kind.
- Page body content.
- Spaces holding customer-facing or regulated content.
Retention
No comment text persisted. Aggregate signals only.
Privacy considerations specific to Confluence
- Atlassian Marketplace data residency selections respected.
- Confluence has the same admin-pre-screen requirement as SharePoint and Notion — pre-flight to identify regulated spaces.
What the customer does at install time
- 1.Site admin installs the Marketplace app.
- 2.Admin selects spaces to connect.
- 3.Admin maps spaces to internal teams.