Distribution and publishing

Once a production finishes the pipeline and clears the final gate, JARAI distributes it to your connected channels and tracks the results — automatically, if the account has auto-publish turned on. This page covers that flow end to end.

🎬 Publish to your channels

Prefer to read? Open the step-by-step transcript

1. Connect your channels once via OAuth — Accounts → pick the account → Connected Platforms.
2. Finish a production. With auto-publish on, distribution starts as soon as the pipeline gate passes; with it off, click Approve distribution on the production’s page.
3. Use Review & Publish on the production’s page to acknowledge rights warnings and deselect any platform you don’t want this production to go to.
4. JARAI posts to each in-scope channel and records the post link for each, in the production’s Publications section.
5. Track publications + engagement on the Distribution dashboard.

Before you can publish

You need at least one connected channel. Connecting is a one-time OAuth step per platform — see Connected platforms. After that, with auto-publish on, publishing happens automatically once a production clears the pipeline gate.

Choosing platforms and completing rights review

1. Open the finished production and review the deliverables — preview each platform variant on the production’s page.

2. Open Review & Publish (top of the production’s page) and choose platforms. By default JARAI publishes to the channels in scope; you can deselect any platform you don’t want for this production. Deselected platforms are suppressed (not published); the rest go ahead.

3. Complete rights review in the same drawer — acknowledge any advisory warnings (copyright/likeness/attribution) surfaced per platform. See Approval and rights review for the customer-side view of the same gate.

Auto-publish off

If the account’s auto-publish is off, a finished production waits in PendingApproval instead of distributing. Its page shows Waiting for your approval to distribute with an Approve distribution button — the account’s CustomerAdministrator, an assigned AccountOperator or a platform admin clicks it, and distribution starts. To stop a held production from being published at all, use Cancel Production. To have future productions ship without this step, turn auto-publish on for the account (see Account settings).

What happens on publish

• JARAI posts the platform-specific variant (correct aspect ratio, duration, and SEO metadata) to each connected channel.
• It records each publication — platform, status, any failure, when it published and a link to the post — in the Publications section of the production’s page.
• Engagement and revenue flow back in and appear on the Distribution dashboard.

Tracking results

Use Dashboards → Distribution to see what published where and the recent-publications list (platform, account, timing, views, revenue). The Avatar performance dashboard breaks results down by avatar and platform.

When a publish doesn’t go through

• Channel disconnected / token expired → reconnect it (Accounts → the account → Connected Platforms). JARAI refreshes tokens automatically where it can, but a revoked authorisation needs re-consent.
• Publication failed or suspended → open the production’s Publications section and click Retry on that row once the cause is fixed.
• Marketplace listing pending review → stock-marketplace publications (image/video stills) sit in Pending while the marketplace’s own editorial review runs. JARAI doesn’t yet pick up the marketplace’s decision automatically, so check the listing on the marketplace itself.
• Distributor requires manual submission → some distributors have no publish API, so the publication waits in PendingManualDistribution and JARAI raises an alert. Submit the content on that distributor’s own web portal, then click Mark as distributed on the row in the production’s Publications section and enter the reference the distributor gave you — JARAI then tracks it like any other publication.
• Nothing in scope → make sure at least one connected channel was selected before publishing.

Note

Distribution runs after the production pipeline completes — it’s a separate stage. With auto-publish on, it starts as soon as the pipeline gate passes and does not wait for a separate manual approval step.