Currently, the Asana Slack integration requires broader permissions than some organizations are comfortable granting. Slack’s granular/optional scopes model would allow administrators to provide only the permissions required for the specific Asana functionality being used.
Use case:
For organizations with strict security and governance requirements, administrators need the ability to limit third-party application permissions based on least-privilege principles. Supporting optional Slack scopes would make it easier to deploy and approve the Asana integration while maintaining appropriate security controls.
Requested functionality:
Support Slack’s granular/optional OAuth scopes for the Asana app.
Allow administrators to select or restrict individual permissions where supported.
Business impact:
This would make the Asana Slack integration easier to approve and deploy in enterprise environments with strict security requirements, while giving administrators greater control over application permissions.