Skip to content

feat: add users:read.email scope to default Slack app manifests#287

Open
blinkagent[bot] wants to merge 2 commits intomainfrom
feat/add-users-read-email-scope
Open

feat: add users:read.email scope to default Slack app manifests#287
blinkagent[bot] wants to merge 2 commits intomainfrom
feat/add-users-read-email-scope

Conversation

@blinkagent
Copy link
Contributor

@blinkagent blinkagent bot commented Mar 2, 2026

Summary

Add the users:read.email OAuth scope to all default Slack app manifests and templates.

Why

The users:read.email scope is required to access the email field in user profiles returned by the Slack Web API (users.info, users.list). Without it, the email field is omitted from API responses even when users:read is present.

From the Slack docs:

Apps created after January 4th, 2017 must request both the users:read and users:read.email OAuth permission scopes simultaneously when using the OAuth app installation flow to enable access to the email field of user objects.

Changes

Added users:read.email to the bot scopes in:

  • internal/site/lib/slack-manifest.ts
  • packages/blink/src/cli/setup-slack-app.ts
  • packages/slack/example-manifest.json (both bot and user scopes)
  • packages/blink/src/cli/init-templates/scout/AGENTS.md
  • packages/blink/src/cli/init-templates/scratch/AGENTS.md
  • packages/blink/src/cli/init-templates/slack-bot/AGENTS.md

Note

Existing Slack app installations will need to be reinstalled for the new scope to take effect.


Created on behalf of @matifali

Add the users:read.email OAuth scope to all default Slack app manifests and templates. This scope is required to access the email field in user profiles returned by the Slack Web API (users.info, users.list). Without it, the email field is omitted from responses even when users:read is present.
@vercel
Copy link

vercel bot commented Mar 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
blink Ready Ready Preview, Comment Mar 2, 2026 2:09am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants