New scope required for workspace token-based chat operations (API Preview)
We're simplifying some permission scopes as part of the workspace apps developer preview.
chat:write represents your app's ability to post messages in the channels and contexts granted to it.
Your app still uses
chat.postMessage and other methods the same way as before.
Slack apps that are not part of the developer preview are not impacted by this change. Bot users are also left unharmed.
chat:write:bot remain functional, distinct OAuth scopes for traditional Slack apps.
We automatically migrated existing grants for
chat:write. You won't need to re-negotiate existing workspace token installations.
If your workspace app requests the
chat:write:user scope to gain the ability to post messages, you'll need to request
chat:write instead. It's a drop-in replacement.
This change already happened, today, on January 11, 2018.
Something amiss? Let us know.Review other recent updates