Slack cuts Marketplace app listing requirement to 5 workspaces on August 11, 2026
The main difference today is simple: Slack reduced the Marketplace submission requirement from 10 to 5 active workspaces, effective August 11, 2026, as noted in Slack’s developer changelog, while its earlier policy page documented the prior 10‑workspace threshold. This is a small but meaningful shift for developers shipping apps into the Salesforce‑owned Slack ecosystem, especially AI agents and workflow utilities that need real‑world usage before review.
Slack Marketplace requirement now set at 5 active workspaces
Slack confirmed the change in its developer updates, stating the Marketplace install requirement would drop to five active workspaces as of August 11, 2026; the prior policy required 10 installs before submission, which is still reflected in the older installation requirement overview. In practice, this lowers the early distribution hurdle for indie builders and small vendors who have struggled to recruit double‑digit testers across unique workspaces before they can even enter the review queue. The update appears alongside other Marketplace process clarifications on Slack’s developer changelog.
What the lower threshold changes for Salesforce and Slack developers
For teams building conversational add‑ons, AI agents, or data‑sync integrations that complement Salesforce, the new floor accelerates time to a credible listing. You still need external validation across multiple independent workspaces, but five tenants is far easier to assemble through customer design partners, open betas, or partner networks. That means less time gate‑kept by pure distribution and more time spent hardening install flows, permissions, and billing.
Review standards, security scopes, and listing quality bars are unchanged
The policy shift doesn’t relax core review expectations. Slack’s Marketplace still enforces scope minimization, quality criteria, and storefront hygiene outlined in its app guidelines and review guide. In practice, that means:
- Proving least‑privilege scopes and a clear value case for any elevated permissions
- Delivering a clean OAuth flow, install success page, and onboarding inside Slack
- Demonstrating reliability across the five testing workspaces, not just your dev org
Practical rollout notes and how to avoid rework
- Treat “five workspaces” as your minimum proof set, not your target. Apps that pass review typically show consistent behavior across different admin settings and message retention policies.
- Expect scrutiny on data access and storage for AI‑assisted features. Reviewers will compare requested scopes to what your listing claims the agent actually does.
- Reuse the same fundamentals Slack has documented for Marketplace launches in its submission best‑practices and platform overview for the Slack Marketplace. Those patterns cut back‑and‑forth during functional review.
Why this matters inside Salesforce’s product story
Slack is Salesforce’s conversational surface for AI agents and workflow automation. Lowering the Marketplace bar from 10 to 5 active workspaces should widen the funnel of third‑party agents and data connectors that plug into Salesforce customer environments, without diluting review rigor. It’s a pragmatic tweak that makes it easier to get from prototype to listed app while keeping the same security and quality expectations in place.
Share With Others
Platinum
