Skip to main content
Publishing presets control whether theStacc generates scheduled content and whether a finished draft needs approval. Choose Manual to work on posts yourself, Draft for me to review generated drafts, or Full autopilot to send generated posts into publishing without that approval step. Open Publishing in the Content SEO section of the sidebar. Check the selected project before changing How should posts go out? A preset belongs to that project, so another project’s settings can differ.

The three presets

Manual

Manual turns auto-generation off and selects manual publishing. Use it when you want to decide which posts to generate and when to publish them from the dashboard. Selecting Manual does not require a connected destination; sending a post to a website still requires an appropriate publishing setup. Manual is also a useful starting point while you configure a destination or review your first drafts. Account access, quota, and publishing checks still apply to actions you trigger yourself.

Draft for me

Draft for me turns scheduled auto-generation on and selects approval-required publishing. Finished drafts wait in Pending Review rather than going straight from generation to automatic publication. Read the draft, make edits, and approve or reject the version you have reviewed. Use this preset when someone needs to check sources, offers, product details, language, or professional requirements before publication. Approval is a workflow decision, not a factual or specialist review performed by the software.

Full autopilot

Full autopilot turns auto-generation on and selects automatic publishing. A successfully generated post can enter the publishing queue without a separate human approval action. Choose this only when the project’s content requirements and destination are ready for that workflow. Automatic publishing does not certify accuracy or guarantee delivery. Account eligibility, connection failures, and configured compliance holds can still stop a post.

What each preset actually changes

A preset combines Auto-generation, which controls scheduled writing, and Publishing mode, which controls the next step for generated content.

Publishing preset settings

PresetAuto-generationPublishing mode
ManualOffManual
Draft for meOnApproval required
Full autopilotOnAuto
The current settings screen saves these values through separate requests. A change can therefore partially apply if one request succeeds and the other fails. The selected preset is not conclusive proof that both saved values agree, especially after an error. If a save fails, stop before relying on the new workflow. Reload the page, inspect the status information, and ask a project admin to confirm or correct the settings. Do not assume that the previous preset was restored automatically.

What happens to your posts in each mode

Manual

New scheduled writing is disabled when the saved auto-generation setting is off. Work already underway or already queued for publishing can continue. Switching to Manual is not a cancellation action for an existing publishing queue. If your goal is to prevent a particular post from going live, inspect that post’s status and schedule as well as the project settings. Do not rely on the preset switch alone to stop it.

Draft for me

New drafts generated through the review-first workflow wait for your decision. Approve moves a reviewed draft toward publication; it does not mean the page is already live. Scheduling, a manual publishing action, destination availability, and configured publishing checks affect what happens next. Follow Draft & Approval Workflow for the review steps. Check Blog Status Lifecycle when distinguishing a draft waiting for review from an approved or scheduled post.

Full autopilot

Successfully generated content is handed to publishing without waiting for a human to approve it. Check the post’s status afterward. A generation success and a publishing success are separate outcomes; a failed destination request can leave the content generated but not delivered. When View Live is available, open the destination and inspect the actual page. A recorded publishing result does not independently confirm every downstream build, webhook handler, or CMS site update.

You need a destination for the automated presets

The settings screen requires an active destination before enabling Draft for me or Full autopilot. Use the Destination section on the same page to connect or inspect it. Supported connections shown there include WordPress, Webflow, Ghost, Zepio, Shopify (shown as Beta), and custom webhooks. Check the destination for the selected project, including its URL and connection state. A destination being listed does not prove that its credentials remain valid or that the receiving website will publish the next request successfully. See Publishing for setup and Publishing Errors & Retries if a post fails to arrive.

Only one preset per project, and who can change it

The screen presents a single preset choice for a project. Project admin access is required to change these settings; members without that access can view them. If you cannot change the preset, ask a project admin rather than attempting to bypass the restriction. Changes affect the settings used by subsequent work. They do not remove drafts, establish that past content was reviewed, or cancel every operation already in progress.

How to set or change your publishing mode

  1. Select the correct project and open Content SEO > Publishing.
  2. Inspect its destination before choosing an automated preset.
  3. Select Manual, Draft for me, or Full autopilot.
  4. Read the confirmation dialog and confirm the intended behavior.
  5. Check the resulting status information. If the save reports an error, reload and verify the settings before continuing.
  6. Review any existing scheduled or publishing posts separately when changing how the project should operate.

A quick way to choose

Choose Manual while setting up or when you want to trigger the work yourself. Choose Draft for me when a reviewer must decide what is ready. Choose Full autopilot when the project can send generated posts into publishing without that approval step. For example, a review-first workflow is appropriate when a draft contains an offer that a team member must verify. This is an illustrative decision, not a claim that approval automatically checks the offer or meets a professional review requirement.