Integration · Project management
On roadmap — not yet shippedClarityLift + Asana
Asana task-comment signals for project-team friction. Roadmap — not yet shipped.
Signals derived from Asana
Team friction (task-comment tone)
Communication health (response times)
Silence (project queue stall)
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.
projects:read
List projects
tasks:read
Read task metadata and comments
users:read
Resolve users for the consent gate
Data flow, end to end
- 1Workspace admin installs the ClarityLift Asana integration.
- 2Admin selects projects to connect.
- 3Asana delivers task-comment events via webhook.
- 4Aggregate signals derived from comment threads.
What ClarityLift does NOT read on Asana
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.
- Task descriptions and body content.
- Project names containing client identifiers (pre-screen recommended).
- Personal task-comment threads.
Retention
No comment text persisted. Aggregate signals only.
Privacy considerations specific to Asana
- Asana projects often contain client-facing context — admin pre-screen is required.
- OAuth tokens encrypted at rest.
What the customer does at install time
- 1.Workspace admin installs the integration.
- 2.Admin selects projects to connect.
- 3.Admin maps projects to internal teams.