This guide explains the limits of Ellie's autonomy: what she can do on her own, what always waits for your approval, and which controls you can use when you want tighter review.
What Ellie does on her own
Ellie can read your connected code and prepare documentation changes from it, but her access is read-only. She never changes your repository, opens pull requests, or commits code.
When Ellie generates content for your help centre, nothing goes live on its own. New generated articles arrive as drafts or in a needs-review state. The finish screen makes this explicit: they are drafts until you publish, so your help centre stays empty until then.
Ellie can also check for documentation changes after a push to the branch your project tracks. Pushes that happen within about 10 minutes are grouped into one run. You can also start a check yourself from Project → Overview with Check latest push. Results appear under Since your last push.
Depending on your maintenance settings, Ellie may apply some article edits automatically as tracked, revertible revisions. This applies only to edits to existing articles, and only when the article is unlocked and the change is suitable for auto-apply. New articles and removals always wait for your approval.
What always waits for approval
Some actions are always held back for review.
Publishing is one of them. Nothing is published unless you click Publish or Publish all, or you tell Ellie to publish in chat or another AI tool. In chat, publishing always asks first.
New features also wait for review. They become New article suggestions. They are never auto-published.
Archiving is never immediate either. If you ask for archiving, Ellie creates a suggestion for you to accept or dismiss.
Uploaded screenshots also stay under your control. If a screenshot was uploaded by you, it carries a yours chip. If a later push appears to affect it, Ellie does not replace it automatically. She creates a Screenshot refresh suggestion instead.
Locked articles always stay review-first. When an article is locked, Ellie only suggests changes and never applies them automatically.
What can happen immediately when you ask in chat
In chat, Ellie can carry out some structural changes straight away, but only when you ask. This includes renaming, moving, creating collections, deleting empty collections, publishing and unpublishing.
After one of these actions, Ellie offers Undo in chat so you can reverse it with the opposite change.
Publishing still requires a confirmation step. Ellie asks before she publishes or unpublishes.
Project control: doc maintenance
Use Project → Settings → Automation to choose how Ellie handles maintenance after code changes.
The Doc maintenance card controls how article edits apply when your code changes.
Approve first is the default. Every change waits for your review as a suggestion. Nothing changes without you.
Confidence-based lets high-confidence edits apply automatically while uncertain ones become suggestions. In this mode you set Auto-apply at ≥. The value can be from 0 to 1 in steps of 0.05, and the default is 0.8.
Fully automatic applies all eligible edits immediately as tracked, revertible revisions. Even here, locked articles and screenshots you uploaded still stay suggestion-only.
Automatic edits still have limits. Ellie only applies an edit by herself if the article is not locked, the change is small relative to the current article length, and the edit does not introduce problems into customer text such as a raw route or an endpoint. In Confidence-based, the edit must also meet your threshold. Anything outside those rules becomes a suggestion instead.

Article control: lock one article
If you want one article kept out of auto-apply, lock it in the editor header.
When the article is locked, the message says Ellie will only ever suggest changes to that article, never apply them. When it is unlocked, Ellie may apply tracked auto-edits again, depending on your maintenance mode.
Locking affects only that article. It does not turn off suggestions or automatic handling for the rest of the project.
Screenshots: what Ellie leaves alone
Pinned screenshots are left alone completely. If you pin a screenshot, Ellie never auto-refreshes it and never suggests replacing it.
A screenshot uploaded by you is also protected from automatic replacement. If a product change makes it look outdated, Ellie offers a suggestion so you can decide whether to refresh it.
Screenshots captured by Ellie work differently. If a user interface change affects one of Ellie's own screenshots, it can be marked stale and recaptured automatically. Screenshots that were not affected are left as they are.
Pre-release features
The Pre-release features card in Project → Settings → Automation controls what happens to docs for a feature you have marked pre-release on the Features page.
Hold as drafts is the default. Articles for that feature stay unpublished until you mark the feature released.
Publish with a label publishes those articles with a visible marker. You can set Label text, up to 24 characters, and the default text is Pre-release. This option requires the Growth plan or higher.
Internal-only features are still never published.

Roles, sample data and simulated integrations
In Project → Settings → Product → Roles, you list the roles your code checks. For each role, choose whether it is Your team only, Customers, or Not a login role.
This matters because customer docs should only describe what customers can see. Once any role is marked Your team only, Check customer docs scans existing articles for mentions of roles and screens not available to customers and raises edit suggestions.
In Project → Settings → Automation, the Sample data card lets you add optional guidance for the example data Ellie creates in the sandbox. This takes effect on the next seed run.
The Simulated integrations card is an on or off switch for sandbox projects. It controls whether Ellie fakes a connected third-party account so connected screens can be captured. Those screenshots are marked in the editor only.
Undo and restore
Even when Ellie applies an automatic edit, it is still tracked and revertible.
Open History (N) on an article to see revisions labelled by their cause, such as code changes, accepted suggestions, founder edits or manual requests. Choose Restore to make an earlier version the current one as a new revision.
Good to know
Can Ellie ever publish without me?
No. Publishing happens only when you do it yourself or explicitly tell Ellie to do it.
Does locking an article turn Ellie off for the whole project?
No. It protects only that article.
Where do I make project-wide automation choices?
Use Project → Settings → Automation.
Is there any irreversible control here?
Yes. Project → Settings → Danger zone → Delete project permanently removes the project and everything generated for it, including articles, screenshots, revisions and onboarding history.