Problem

The Outlook AI connection for ClickUp Brain currently requests the Mail.Send permission. This means connecting a mailbox gives ClickUp the ability to send email as the user. For teams with security or compliance requirements, that is a blocker. In my case, the send permission prevents me from connecting my mailbox at all.

There is currently no drafts-only consent option. The read-only Outlook Connected Search connection is not a workaround, because it cannot save drafts.

Requested feature

A drafts-only Outlook connection that lets Brain create and update drafts in the user's mailbox, but never send email. The user reviews each draft in Outlook and sends it themselves. On the Microsoft side, this should be achievable with a scope such as Mail.ReadWrite, without Mail.Send.

Broader suggestion

Let users and admins choose individual OAuth scopes per integration in the App Center, instead of an all-or-nothing consent. This would help with Outlook and with any other integration where the default permission set is wider than the intended use case.

Why it matters

Many organizations apply least-privilege principles and will not approve an integration that can send email on a user's behalf.

Human-in-the-loop sending (AI drafts, human reviews and sends) is the safer pattern for AI-generated email, and it is what most teams want anyway.

The current workaround is copying Brain's text into Outlook by hand, which loses most of the value of the integration.

Use case

Brain drafts replies or follow-ups from task and project context and saves them as Outlook drafts. The user checks them in Outlook and sends them manually. Nothing is sent without explicit user action.