Review and share your work
Check the details and choose where approvals belong in your workflow.
Decide what needs your review
Assistant and Co-pilot ask before external or irreversible actions. Autopilot can publish automatically when your effective settings permit it. Keep any action, channel, or product that needs a person’s decision set to Needs approval.
Start with the facts
Check every product claim against a current source. Pay particular attention to numbers, dates, supported integrations, and promises about what a feature does. Product context helps ground a draft; an editor still needs to check it.
Make feedback actionable
Explain the change you want and why. “Replace the opening with a concrete customer problem” gives a clearer revision target than “make it punchier.” Review the revised version before moving it forward.
Check the destination before approving
Approval can do more than change a status. Depending on your workspace and the content type, it may trigger publishing or create a pull request. Confirm the configured destination and action before you approve.
For website articles, a configured GitHub repository and credentials can let Clara create a pull request for review in your existing workflow.
Share through your workflow
Use the publishing integrations available to your workspace, or export a supported format for your own process. A finished draft does not mean an account is connected or that a post has gone live. Check the outcome in the destination service.
Keep useful context for next time
When feedback reveals a recurring preference, add it to your brand guidelines or reusable instructions. When it reveals a factual gap, update the product sources. The next brief should start with that clearer context.