concept · explanation
Billing, entitlements, and limits
Understand how billing, entitlements, and limits works in Slash Social.
Your organization’s plan decides what Slash Social allows before a Slack action completes. Billing, usage counters, and feature gates all roll up to the organization, not to an individual Slack workspace or brand.
Overview
One organization holds the subscription, tracks usage, and controls plan access. Every Slack workspace and brand inside that organization shares those limits. Workspace admins still run day-to-day content inside each brand, but plan changes, invoices, and payment fixes are organization decisions.
Self-serve plans are Free, Starter, Team, and Scale. Each plan bundles numeric caps (scheduled posts, AI generations, brands, workspaces, connected profiles, and related limits) with included features. Exact numbers live on the Plans and Limits reference pages.
How it works
Limits are counted caps. When the organization reaches a limit, Slack blocks the action and shows quota feedback. Some paid-plan limits display as unlimited in the UI. Limits apply org-wide: a scheduled-post cap counts posts across every workspace, not per Slack team.
Included features are on or off by plan. An action that requires a locked feature shows an upgrade prompt instead of completing. For example, Advanced analytics is included on Team and Scale and not on Free or Starter.
Platform access is also plan-scoped. Self-serve plans support nine networks: Instagram, TikTok, X, Facebook Pages, LinkedIn, YouTube, Threads, Pinterest, and Bluesky. Free includes the same set except X; Starter and above include all nine.
Payment status gates expensive work. When billing status is past due, paid features and costly operations stop until payment is fixed in the customer portal. Active and trialing statuses run normally within plan limits.
Admins with billing access open Settings, then Billing & Plan from /social. That surface covers current plan details, usage, upgrade options, checkout, the customer portal, billing history, and organization privacy actions such as data export and deletion requests.
The upgrade flow opens a plan comparison modal with prices and highlights your current plan. Checkout can deliver a payment link by DM for the selected plan and billing interval. Addon and history modals live in the same billing area when your org uses them.
Examples
A creator on Starter schedules posts until the org hits its monthly scheduled-post cap. The next schedule attempt returns quota feedback. An admin upgrades the plan or waits for the counter to reset.
An approver opens Insights on Free. Advanced analytics cards are gated. The user sees an upgrade path because that feature requires Team or Scale.
An org on Team with past due billing tries to run AI generation. The action blocks until the billing owner fixes payment through the portal linked from Billing & Plan.
A marketing lead checks usage before month end. The usage modal in billing shows scheduled posts and AI generations consumed org-wide, so they can forecast whether an upgrade is needed before creators hit walls.