## Summary Based on https://gitlab.com/gitlab-org/gitlab/-/issues/351384#note_874131337, the clearest path forward to rebuilding/refactoring the Slack App and unlocking new feature capabilities is to migrate the [current Slack App from Classic to Granular Bot Permissions](https://api.slack.com/authentication/migration). ## Next Steps - [X] We'll release the initial iteration internally for dogfooding to the GitLab Workspace only in %"15.0" - this contains the GBP App update and will require Slack Workspace Admins to re-install the app manually - [ ] We'll complete https://gitlab.com/gitlab-org/gitlab/-/issues/356000 - [x] We'll then release the same app globally in %"15.1" through the Slack Marketplace (which requires Slack's review review/approval) - this would be a soft release, no major announcement - [ ] Then implement the mass-update of `SlackIntegration` records (which would enable only Slack Workspace admins to re-install the Slack App when there are updates vs individual project owners having required actions) - [ ] Then work on Link Unfurls and release the iteration and make a more public announcement ## Risks - As per Slack's documentation, [any app that isn't using granular bot permissions after May 27th](https://api.slack.com/authentication/migration?utm_medium=referral&utm_source=apiblog&utm_campaign=fy20-Q401-granular-permissions#faq_directory_schedule) will be _delisted_ from the marketplace. ## Links and resources - General migration guide: https://api.slack.com/authentication/migration - Gitlab-specific migration guide: https://docs.google.com/document/d/1wXePct8JiG1qrLAgjWX3sy8Xoi8gMHlImDBFxJAcZfs/edit - GitLab Ecosystem workspace: https://app.slack.com/client/T0187G888CD - Administration for the Slack app: https://api.slack.com/apps/A676ADMV5