Closed stokedout closed 6 days ago
Hi stokedout,
That sounds right to me; add the new scopes to the app manifest you use as a template, include the new scopes in your install URL. Add the new scope to each existing app's config and update. If new user scopes are added, each user might need to go through the Oauth flow again to accept the new scopes. I'm not sure about any actions in Django admin; the app bot users should be updated when the app is reinstalled.
Yes, if an app changes, it changes for all users
👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.
As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.
Ello... I've adopted code based on the oauth_app example in this repo with a slack bot aka new app manifest being created per project in our system.
When we want to enable Slack integration for a client it generates a new app in api.slack.com/apps and it's based on a hardcoded app manifest in our codebase.
Several apps have been created and several clients use them. My question is, if I want to add new permission scopes do I need to:
Bot permissions
fields inSlackBot
andSlackInstallation
in django admin for every bot?Also, I've heard that if one user in a slack team reinstalls the app/bot then the others don't need to. Is this true?