Skip to main content
For small teams

Team workflows without enterprise ceremony

Two to ten people, one public voice: roles shape who drafts and reviews, advisory decisions are recorded, publishing stays separate, and the calendar shows receipt-backed delivery state.

How does a team share one voice?

The workspace Brand Kit is the team's shared voice context: identity, tone, audience, and references defined once and used by supported generation flows. It promotes consistency, but generated output still requires human review.

Who gets to publish?

Whoever the roles say. Invitations bring members in with defined roles; approvals add an advisory review record; publishing remains a separate action; and connected accounts are workspace-level, so leaving members do not take credentials with them.

  • Workspace invitations with role assignment
  • Recorded advisory review decisions
  • Workspace-level platform connections, revocable anytime
  • Explicit schedules; posts editable until delivery
  • One calendar of queued, delivered, and failed posts

What does the team see after publishing?

Successful deliveries store receipts, metrics can be synchronized on demand where supported, failures stay visible until handled, and publishing uses durable idempotency reservations to reduce duplicate risk, and ambiguous provider outcomes stay reconciliation-required instead of being reported as confirmed success. Notifications keep reviewers and owners in the loop.

Frequently asked questions

How do teammates join?

By workspace invitation with a role. Roles control drafting, approving, connecting accounts, and publishing; workspace data is isolated by database-enforced tenant policies.

Can we require review before posts go out?

You can route social drafts, documents, or media through an advisory review and record who decided and when. This does not freeze the content or enforce a publishing gate; publishing remains separate.

Do we pay per seat?

Plans are recurring subscriptions for the workspace with AI work metered through a shared credit ledger — a hold before work, settled on success, released on failure, auditable by the team.

What if two people publish the same draft at once?

Durable idempotency reservations make recognized concurrent or retried attempts safer and reduce duplicate risk. Ambiguous provider outcomes require reconciliation before another attempt.

Related pages

Write once. Post everywhere.

Draft in your brand voice, approve what matters, and publish with confirmed delivery state.