New scope required for workspace token-based file write operations (API Preview)
This feature was exclusive to our workspace apps developer preview. The preview has now ended, but fan-favorite features such as token rotation and the Conversations API will become available to classic Slack apps over the coming months.
We're simplifying some permission scopes as part of the workspace apps developer preview.
files:write represents your app's ability to upload and manage files.
Experiencing déjà vu? This is just like that time we did this for
Your app still uses
files.upload and other methods the same way as before.
files:read is still
files:read, whether you're working with a workspace app or otherwise.
Slack apps that are not part of the developer preview are not impacted by this change. Bot users are also left unharmed.
files:write:bot remain functional, distinct OAuth scopes for traditional Slack apps.
We automatically migrated existing grants for
files:write. You won't need to re-negotiate existing workspace token installations.
If your workspace app requests the
files:write:user scope to gain the ability to post messages, you'll need to request
files:write instead. It's a drop-in replacement.
This change just happened, today, on April 17, 2018.
Something amiss? Let us know.Review other recent updates