Settings
Integrations
Each connection states the highest band it lets the engine reach, and the exact scopes it holds.
Band is a property of the connection. GitHub is the only integration that reaches the gated band, and reaching it still means a human approves in this dashboard before a PR is opened. Disconnecting GitHub does not disable fixes — every fix still renders as a diff you can apply yourself, and as a coding prompt.
GitHub — acme/site
not connectedgatedNot connected. Connect GitHub to let drafted fixes become pull requests.
Turns a drafted fix into a real pull request. The app can open PRs; it cannot merge them, and no scope we request would let it.
contents:writepull_requests:writemetadata:read
Google Search Console
not connectedreadNot connected.
Supplies classic rank and impression data so the SEO screen can show where ranking and citation disagree.
webmasters.readonly
CMS (Contentful-compatible)
not connectedgatedNot connected.
Lets request_publish put an approved content change live. Without it that tool fails closed rather than pretending to work.
Slack — #growth
not connectedreadNot connected.
Pushes alerts into a channel. Read-only in every direction — nothing in Slack can drive the engine.
incoming-webhook
What we never ask for
The scopes we deliberately do not request, and why.
- Merge or write to a default branch — Every change lands as a PR against a branch. Merging is yours.
- Delete anything — No integration we request carries a delete permission on any surface.
- Read private repository source beyond the target repo — The GitHub app is installed per-repository, not per-organisation.
- Write to Slack — Alerts are one-way. A Slack message can never trigger a fix.