concept · explanation

Slack surfaces and entry points

Understand how slack surfaces and entry points works in Slash Social.

Overview

You need to reach Slash Social from a channel, App Home, a DM, or a message without hunting for the right button. Slash Social spreads work across several Slack surfaces. Each surface fits a different kind of task: daily queues on App Home, focused forms in modals, and quick launches from slash commands or shortcuts.

How it works

Where work happens in Slack

Slash Social uses several Slack surfaces:

  • App Home is the daily hub for work center cards, queues, and setup. Plan views such as the weekly rail also start here.
  • Modals handle create, review, settings forms, and list-detail flows. The create modal stacks with media and preview steps when needed.
  • Channel messages carry approval cards, inbox alerts, and team notifications when your workspace routes them there. Approval threads let reviewers act without opening App Home.
  • Bot DMs accept link intake and library saves when you message the app directly.
  • Message capture paths let you paste a Slack message link or message text into create, ideas, briefs, or knowledge flows.

Most tasks start from App Home or the Command Palette. Modals open on top when a flow needs focused input.

Public slash commands

Three commands are registered on the public Slack app manifest:

CommandTypical use
/socialOpen the Command Palette and search for a task
/social-createStart the create flow
/social-approveOpen pending approvals

Additional tasks appear inside /social after you run the palette. Commands not on the public manifest are not typed directly; search for them in the palette instead.

Shortcuts and fallbacks

The global shortcut Open Command Palette runs the same search surface as /social when Slack shows it in your workspace.

To capture a Slack message as content input, use message shortcuts, /social, DM intake, or App Home create paths with the message link or text.

Where you see it

Creators use App Home or /social-create when they need the full create flow. Approvers use /social-approve, approval cards, or App Home review queues. Admins start most setup and settings work from App Home because those flows need brand, account, and permission context.

Why it matters

Picking the right entry point saves clicks and keeps context. App Home shows what needs attention today. Modals keep create and settings work contained. Channel threads keep approvals where the team already discusses content.

Slash commands and the palette give you fallback paths when you are already in a channel and do not want to switch to App Home. /social-create and /social-approve map directly to the most common creator and approver tasks.

Knowing which surfaces update asynchronously also prevents confusion. App Home refreshes after background work. DMs may carry completion or failure notices when modals cannot stay open. A post you start from a channel may end in draft saved, queued, pending approval, or generation failed even after the modal closes.