concept · explanation

Work Objects and Slack Lists

Understand how work objects and slack lists works in Slash Social.

Overview

Slash Social can mirror social workflow state inside Slack using rich cards and native Lists. Teams see status, ownership, and next actions where they already work instead of hunting through separate tools.

Two surfaces share the same brand-scoped records:

  • Work Objects: entity cards for a single record or shared link
  • Slack Lists: tabular backlogs the product maintains per brand

Both are optional complements to App Home, DMs, and /social modals. They do not replace those entry points.

How it works

Work Objects

Work Objects are Slack entity cards tied to a record in Slash Social. They show live fields such as status, owner, campaign, platform, and next action, and refresh when the underlying record changes.

Examples in the product today include:

  • Content items moving through create, review, and publish
  • Client approval cards for external review flows on Team and Scale plans
  • Inbox conversations when unified inbox Work Object rollout is enabled for the org
  • Link unfurls when someone shares a Slash Social URL in a channel

Work Objects appear in channel messages, Slack detail panes, and link previews depending on context. A stale or missing preview does not always mean the record is wrong in App Home. See Work object preview missing for recovery steps.

Slack Lists

Slack Lists are native Slack tables the product can maintain for a brand:

  • Pipeline: posts in flight, including approval status
  • Ideas: captured concepts linked back to the social workflow
  • Partner Deliverables: creator and partner work when that workflow is enabled

Lists are optional. DMs, App Home, the Command Palette, and channel cards work without them. When Lists are enabled, rows stay aligned with the same brand-scoped records you see elsewhere. Fields typically include owner, state, campaign, and platform so the team can sort and filter inside Slack.

Provisioning needs a Slack workspace with Lists access, an installed app, and a resolvable posts channel for the brand. Brands without a posts channel are skipped until channel setup completes.

How the two fit together

Lists give a tabular backlog view inside Slack. Work Objects give a rich card for one record and for shared links. Both read from the same brand-scoped content and workflow state, so counts and statuses should match App Home when sync is healthy.

If a list is missing or out of date, users can still open records from App Home or /social. When rows stay wrong for more than a day, contact support with the workspace, brand, list name, and one example item.

Examples

Pipeline standup in a channel. The Pipeline list shows twelve posts awaiting approval. A manager shares one post’s link in the team channel. Teammates see a Work Object card with status and owner without opening App Home.

Ideas captured from a thread. A creator drops a concept in Slack. The Ideas list row links back to the social workflow so planners can promote it to a draft when ready.

Client approval in a shared channel. On Team or Scale, an external approval Work Object appears where the client reviews content. Status updates on the card as approvers act, while the Pipeline list row stays in sync.

Link preview for a scheduled post. Someone pastes a Slash Social URL. The unfurl shows platform, slot, and approval state. If the preview lags, check App Home first, then the troubleshooting article linked above.