Supported generation flows use the workspace Brand Kit — identity, voice, audience, references — and adapt drafts natively to each platform instead of cross-posting one text.
Supported generation flows use the workspace Brand Kit: ingest a public website to extract identity, voice, colors, and references, or define them directly. If strict separation between client identities is required, use separate tenant-isolated workspaces rather than relying on an in-workspace brand selector.
drafts adapt natively to X, LinkedIn, Instagram, and Threads formats. Length, structure, and tone follow each platform's conventions — a LinkedIn draft is not an X draft with more words, and an Instagram caption is written for the image it accompanies.
Drafts are the start of the workflow, not the product. Review them, optionally record an advisory decision, then separately schedule an explicit time or publish through connected accounts — publishing uses durable idempotency reservations to reduce duplicate risk, and ambiguous provider outcomes stay reconciliation-required instead of being reported as confirmed success.
Yes. One idea produces separate native drafts for X, LinkedIn, Instagram, and Threads, each following that platform's format conventions — not one text cross-posted four times.
Image Studio generates, edits, and stores image assets in the same workspace using configured AI providers, so an Instagram draft and its image live together and go through the same review.
Configure the workspace Brand Kit before generating. It carries identity, voice, audience, colors, and reference material ingested from your website or defined manually, and supported generation flows use that workspace context.
No. Generated drafts reach a connected platform only through your explicit publish action or a configured schedule. A recorded approval is advisory and does not publish the draft.
Draft in your brand voice, approve what matters, and publish with confirmed delivery state.