concept · explanation

Content lifecycle

Understand how content lifecycle works in Slash Social.

Overview

A single social post moves through several states from first draft to live on a platform. Slash Social keeps the copy, media, campaign context, review history, and selected accounts together so you can create, review, schedule, and recover posts without losing context.

How it works

One post, multiple account destinations

Slash Social stores one post record for the draft: caption, media, campaign context, and review history. The post can include one or more connected accounts and formats. For example, one draft can target Instagram, TikTok, LinkedIn, and other supported networks at once. Each destination tracks whether it is ready, scheduled, published, or blocked.

Creation starts in the Create work center. Review and edits happen in Workflow and approval modals, including inline edit and reject flows. Scheduling and queue placement live in Plan.

You can also start from App Home, bot DMs, or asset pickers when intake paths feed into the same item record.

Typical state flow

Most posts follow this path:

  1. Draft while copy, media, or generation is still in progress
  2. Pending approval when review is required
  3. Scheduled or queued inside an allowed posting window
  4. Published after the platform accepts the post

Branches exist at each step:

  • Generation failed means AI or motion work did not finish. Retry from failed-job views or follow troubleshooting for generation recovery.
  • Publishing failed means the platform rejected delivery. Fix account connection, media, copy, or platform settings before you retry.
  • Rejected, changes requested, or archived posts leave the active queue but keep history for audit and library reuse.

Review workflows can end in approved or rejected before scheduling. Items may also sit in draft saved or queued while you finish edits or wait for a posting window.

Publishing operations

Publishing runs after approval and schedule checks pass. Slash Social verifies account connection, format rules, and cadence windows before it sends content to each platform. Status changes appear in App Home, Plan, approval channels, and Insights once platforms return confirmation.

Approval threads and preview modals let approvers edit copy, reject with reasons, reschedule, or archive while keeping the post history intact. From a review context you can open content preview, review source details, refresh analytics, or schedule from Plan without losing the thread.

Why it matters

The shared post model keeps one source of truth when you post to multiple networks. Editors change copy once. Each destination carries its format-specific requirements. Approvers see the same item in Workflow threads and approval modals that creators opened from Create.

State names also tell you which work center to open. A pending approval item needs Workflow attention, not Plan rescheduling. A queued item is waiting on time or cadence, not on copy edits. Misreading the state leads to duplicate drafts or missed publish windows.

Archived and rejected items remain searchable for review history and library reuse, so teams can learn from past campaigns without cluttering the active queue.