Please note, your app does not need to be listed in the App Directory for it to work for your own or other Slack teams.
Once you've built your app, you can submit it to the App Directory to be used by other Slack teams. We review apps to ensure they provide users with a great experience and comply with our API TOS, Developer Policy and Brand Guidelines.
When submitting, you'll see the comprehensive checklist shown below, which covers the most common points of failure during the review. Follow this checklist to help your app go through the review process quickly and smoothly.
To submit your app:
- Select your app from https://api.slack.com/apps
- Choose Submit to App Directory from the left-hand menu
- Complete the checklist and submit
Once we've reviewed your app, we'll email you. If your app is approved, you can publish your app to the App Directory from your app's configuration page. Your live app's settings will be accessible from the Live app configuration section.
To update your published app:
- Click Edit app on your app's configuration page to create a development copy after you've published it
- Edit your app as needed and test using the credentials of the development app (these changes will not affect the published version of your app)
- Submit those changes for review from the Update Directory app section
You can also remove your published app from the App Directory in the Live App Settings of your app's configuration page.
App Submission Checklist
Review your permission scopes
- My app only uses the scopes that it needs to work.
- I've added all scopes my app requests and reasons for each one.
Review your user experience
- Messages from my app use clear, consistent formatting. (Read up on the formatting and attachment documentation for a refresher. You can also use our Message Builder to see a preview of your messages.)
- Messages from my app don't contain any typos or grammatical errors.
- My app doesn't spam all users on a team either in DM or by email (see API Terms of Service).
- My app uses @-channel or @-here notifications only when truly appropriate.
- My app does not use any Slack team email addresses collected when the app is installed to send emails to those users.
- If my app uses a slash command or bot user, there's a way for a user to ask for help or send feedback within the app.
- I've tested my app on my own Slack team to confirm all its features are functional.
- I've performed a final test before submitting my app, including installing it from scratch using my own instructions and completing the entire onboarding process.
- My app is ready to support a large number of users after listing in the App Directory.
Prepare your App Directory listing
- My app has completed all necessary fields
- My app's name doesn't infringe on a trademark or copyright for any other products or services.
- My app's name isn't the same as a name currently in the App Directory.
- My app has a high quality, distinctive icon that doesn't resemble Slackbot or the Slack icon (see Slack Brand Guidelines).
- My icon doesn't infringe on anyone else's copyright or trademark (including Slack).
- My app has a well written, detailed, and truthful long description of what it does.
- My app's long description includes details about any of the following: paid account requirement, emails from my app, provisioning with a Slack user's email.
Review your installation landing page
- My landing page contains a detailed summary of what my app does and how it integrates with Slack.
- My landing page contains clear instructions on how to install and use my app (e.g. which parts of my app trigger messages in Slack, and which comments a bot responds to).
- My app's landing page displays the Add To Slack button for users to install my app, or has detailed instructions about how to access the Slack button if behind a login page.
Prepare your customer support
- My app links to a page with clear instructions on how to contact your team if they encounter problems or need help.
- My support channel is active, and I'm responsive to new requests.
- Contacting my team for support doesn't require creating a new account of any kind.
- I agree to keep my app updated and my support channel active.
Review and agree to our policies
Help us review your app
We'll also need some information to help us review your app
- Details of any paid test accounts we need to use your service
- Details of any test accounts that might be needed for third-party services
- Details of a new Slack team with your app installed