Optional scopes have landed
Apps can now mark individual OAuth scopes as optional during configuration, giving users more control over data access permissions without blocking installation.
You can now mark individual OAuth scopes as optional when configuring your Slack app! Optional scopes give users more control over what data your app can access during installation, without blocking them from installing your app entirely.
What's changed:
- App configuration: Mark scopes as optional directly from the app settings page or via your app manifest using the new
bot_optionalanduser_optionalfields. - OAuth flow: Users now see optional scopes presented separately during installation and can choose which ones to grant.
- Admin controls: Workspace admins can pre-approve which optional scopes are available to their users when approving apps.
- App manifest: Two new fields—
bot_optionalanduser_optional—are now supported underoauth_config.scopes. See App manifest fields for details.
If your app uses scopes that aren't strictly required for core functionality, consider marking them as optional to improve installation rates. Read more on the Installing with OAuth page.
Source: original entry ↗
More from Slack
Follow Slack to get its new changes in your feed and email digest.
Slack CLI v4.10.0 Released
Slack CLI version 4.10.0 is now available, bringing updates and improvements to the developer tools for the Slack platform.
Slack Code for developers
Slack Code enables deeper collaboration between humans and agents by allowing agents to create ephemeral channels from existing conversations, giving collaborators a shared workspace for coordinated work.
Slack CLI v4.9.0 Released
Slack CLI version 4.9.0 is now available with updates and improvements to the command-line tool for building and managing Slack applications.