Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.socializioz.com/llms.txt

Use this file to discover all available pages before exploring further.

The Publishing hub is the operational overview for day-to-day publishing in SocializioZ. It brings the core lifecycle stages together so you can move from planning to review without jumping across disconnected pages.

​
When to use it

Use the Publishing hub when you need to:
  • See what needs action today.
  • Track posts across draft, pending, scheduled, failed, and published states.
  • Jump quickly to editing, approval, rescheduling, or retry actions.
  • Coordinate publishing work across teammates.
If you need deep calendar planning, open Scheduling and calendar. If you need content editing, open the Post composer.

​
Main actions

​
1) Monitor pipeline status

Use the hub to understand where posts are blocked or progressing:
  • Drafts waiting for completion.
  • Pending items waiting for approval.
  • Scheduled items queued for publishing.
  • Failed items needing retry or fixes.
  • Published items ready for performance review.
This gives teams a single operational picture instead of checking multiple pages manually.

​
2) Prioritize work that needs action

Start with urgent states:
  • Failed posts that missed publishing windows.
  • Pending approvals for near-term campaigns.
  • Drafts that must be finalized before scheduled slots.
Then move to proactive cleanup, such as rescheduling crowded time windows.

​
3) Open and complete next-step actions

From hub entries, jump to the action that resolves the item:
  • Edit content in composer.
  • Approve or reject in approvals flow.
  • Reschedule in calendar.
  • Retry failed publishes.
  • Open published results for verification.

​
4) Keep team workflows predictable

Use consistent naming (titles, campaigns, accounts) so everyone can quickly identify ownership and priority from list views.

​
Important notes

  • The hub is best for operational triage; deep analysis belongs in Analytics.
  • Status reflects current system state, but platform-side delays can affect when final results appear.
  • Items may move between states quickly around publish time; refresh if counts seem outdated.
  • Approval-heavy teams should review pending items early to avoid avoidable misses.

​
Troubleshooting

​
Counts look wrong or stale

Common causes:
  • Recent actions not yet reflected in your current view.
  • Filters narrowing results unexpectedly.
Fix: refresh the page and clear filters before investigating further.

​
I cannot find a post from the hub

Common causes:
  • Post moved to another status after an action.
  • Search/filter terms are too specific.
Fix: remove filters and check the corresponding destination page (calendar for scheduled/failed, published page for live content).

​
A failed post keeps failing on retry

Common causes:
  • Persistent account permission issue.
  • Content still violates platform constraints.
Fix: open details, correct content or account connection, then retry. See Troubleshooting.

​
Practical workflow example

A simple daily routine for teams:
  1. Open the hub and review Failed and Pending first.
  2. Resolve urgent failures (retry or fix content/account issues).
  3. Clear approvals that affect today’s schedule.
  4. Confirm the next publishing window is fully populated.
  5. Hand off published items to reporting or community management.
This keeps execution predictable and reduces last-minute misses.
Last modified on May 16, 2026