Dashboard
Overview
Run publishing, delivery, and access control from one workspace.
No workspace selected
Setup progress
Follow the guided sequence to move from setup to live publishing.
System status
Keep the workspace, plan usage, and delivery health visible.
Last 5 posts
Latest scheduled or published posts across connected accounts.
Next action
The single most important setup action right now.
Recent activity
Webhook deliveries and publish events across the workspace.
Critical blockers
These are the gaps that currently stop the workspace or selected project from moving forward.
Workspace state
Choose an organization to load setup progress.
0%
Setup completion
Usage
Current billing window will appear here.
Workspace settings
Update launch state, use case, and target platforms only after reviewing the current workspace state above.
Project directory
Select a project first, then manage its keys, providers, and delivery readiness.
No projects yet
Create the first project to unlock providers, content intake, and delivery.
Selected project
Choose a project to load API-key, content, and publish readiness.
Project readiness
The selected project should be able to ingest, generate, and publish before you move into delivery.
API keys
Review existing machine credentials first, then issue a new key only when needed.
Issue a new API key
Create project
Project creation is secondary once the directory and selected project state are visible.
Create a new project
Provider workspace context
Select a project to review provider readiness.
Next action
Choose a project to see what is required before starting a provider connection.
Project required
Create and select a project to unlock provider connections.
Connected social accounts
Review connected accounts and pending OAuth work before starting another provider flow.
Provider catalog
Review rollout status only when you need to plan additional provider coverage.
View provider catalog
Start or finalize a connection
Only live-ready providers should be started here. Manual finalize stays available only when an OAuth callback is already pending.
Open provider connection controls
Manual finalize fallback
Content workspace context
Select a project to review intake and preview readiness.
Next action
Choose a project to see what is blocking intake, preview generation, or media preparation.
Project required
Create and select a project to unlock content intake and previews.
Send content via API
Use your project API key to send content into the queue.
curl -X POST https://api.yourdomain.com/v1/content-items \
-H "Authorization: Bearer PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"projectId": "PROJECT_ID",
"title": "Launch your first post",
"canonicalUrl": "https://example.com/story",
"summary": "Short summary for the social preview.",
"platforms": ["x", "facebook"]
}'Content queue
Preview generation
Select a content item
Generation runs
Generation guidance
Select a content item to see what happens next between intake, generation, preview review, and delivery.
Variant previews
Asset library
Upload a new asset
Manual intake fallback
Use this only when upstream ingestion or API-driven intake is not available yet.
Open manual intake form
Delivery workspace context
Select a project to review publish and callback readiness.
Next action
Choose a project to see what still blocks the first reliable publish cycle.
Project required
Create and select a project to unlock delivery operations.
Delivery queue
Selected post
Inspect one post at a time, then schedule, retry, or attach media from here.
Selected post status
No post inspected yet.
Selected post tools
Select a post to schedule or attach media.
Webhook deliveries
Delivery events and retries should be visible before webhook creation is touched.
Event webhooks
Create event webhook
Current invites
Review active invitations first, then issue a new invite only if the current team state requires it.
Create invite
Invite creation is secondary to reviewing current team access and pending invitations.
Open invite creation
Billing and plan state
Billing metadata loads for the active organization.
Provider-backed billing
Review provider status first, then launch checkout or portal sessions only when needed.
Billing providers
Provider availability loads with the billing workspace.
Open provider session controls
Billing metadata
Manual metadata is last-mile administration, not the first thing an operator should see.