Setup for SlackKit

Although SlackKit manages your scopes, you have to add one in your Slack application's settings to start with so that it exposes the form for you to add a redirect URL.

Add channels:read to the scopes section. For the rest, you won't be managing SlackKit's scopes directly since the components will request the scopes they need. Here is the list of scopes and the reasons they're required:

• chat:write: This scope allows your bot to send messages to channels that the bot has been explicitly invited to, including private channels. It doesn't grant the ability to send messages to public channels without an invite.
• chat:write.public: This scope extends the bot's capabilities to send messages to public channels without needing a specific invitation to those channels. It's an addition to the chat:write scope, offering broader access for the bot to interact within the workspace.
• channels:read: This scope allows your bot to list all channels in a workspace and view details about specific channels (like name, topic, purpose, members), but does not grant access to private channels.
• groups:read: This scope allows your app to list all private channels that the bot or user is a member of and to view details about those channels.

You can read more about scopes in general in building a slack app.

Under OAuth & Permissions in the Features sidebar, you need to add a redirect URL so that Knock can receive the Slack OAuth handshake on your behalf.

Copy and paste this redirect URL:

Under Manage Distribution, click the "Distribute app" button which will show you a list of items to complete to activate public distribution. If you've built the app from scratch and completed the previous steps, you should see all of these complete except for "Remove hard coded information."

Check the box and then click "Activate Public Distribution."