Permissions
By default the Agent changes nothing. Chat stays click-to-confirm at every setting, so this page is about the other path: a standing automation, the only thing that can act without a fresh click, and only inside the permission, scope and weekly limit you saved for it.
Permission belongs to one automation and one area of work at a time. There is no switch that lets the Agent do everything. Until the safety rollout reaches your brand, the service also clamps every automation to Suggest only whatever is saved, so the higher rungs may not be selectable for you yet.
Six areas of work
| Area | What it covers |
|---|---|
| Technical fixes | Metadata, schema, crawler files and other mechanical site fixes |
| Page improvements | Changes to an existing page based on its measured gaps |
| Content refreshes | Preparing or updating existing content |
| New content | Preparing a new article or page |
| Getting listed | Drafting outreach for a citation or listing |
| Community replies | Drafting a reply for a community thread |
The split keeps a grant narrow. You might let an automation repair metadata, because the CMS can snapshot and restore it, while keeping new content at drafts and community work at findings only. Raising one area does not raise the others, and a grant belongs to one automation.
The five rungs
On the automation record, open How far it can go. One area expands at a time, and a line is drawn above the first rung that changes your site.
| Rung | What happens |
|---|---|
| Tells you | It tells you what it saw. Nothing else happens. |
| Suggest only | It brings you findings. Nothing changes without you. |
| Prepare drafts | It prepares the work. You approve before anything ships. |
| Prepare for approval | It prepares the change and waits for your approval before applying it. |
| Handle it | It makes changes up to your weekly limit and reports each one. |
Tells you is a whole-automation mode for reporting, not a per-area grant. The four rungs below it are the ones you set per area, and Suggest only is the default for a new automation.
Two limits apply on top of the ladder today. Only Technical fixes and Page improvements can reach a site write at all; Content refreshes and New content stop at a prepared draft even when a higher rung is saved. And Handle it needs automatic revert armed plus a healthy recent record: if the quality check trips, the automation pauses itself instead of continuing.
Lowering a rung is free and never asks for confirmation. It applies from the next check.
Weekly limits
Any rung that can change the site carries a weekly limit for that area. The editor offers 1, 2, 3, 5, 10 or 20, starts at 5, and the service accepts no more than 50.
The count is per automation and per area, so five technical fixes does not eat the allowance for page improvements. Only applied changes count; suggestions and prepared drafts do not. When the limit is full the Agent leaves the work for you with the reason recorded, and the rolling seven-day window frees capacity as older changes age out. Raising the limit is a deliberate edit, never something the automation can do for itself.
What can be reverted
Trakkr applies a change automatically only when it captured the previous value and the connected platform can mechanically restore it. Coverage is uneven.
| Change | Platforms that can revert it |
|---|---|
| Meta title, meta description | WordPress, Webflow, Shopify, GitHub |
| Social preview tags, canonical URL, llms.txt, robots.txt | WordPress, Webflow, GitHub |
| Schema markup | WordPress, GitHub |
| Image alt text | WordPress, Webflow |
| Heading structure | GitHub |
GitHub reverts through a second pull request rather than writing to a live branch. Every row still depends on the connection itself: a WordPress role and a supported SEO plugin, a mapped Webflow image field, the API access a Webflow site has for crawler files. Sites carries the full per-platform detail. A change with no revert path can still be suggested or drafted. It cannot be applied automatically.
Every change says who did it
Where a change lands, Trakkr stamps who executed it (a person or the Agent), who asked for the automation, who approved it, which run and automation it came from, and which rung allowed it. A Handle it change has no individual approver, because the saved grant is the approval. It still records who created the automation and the rung used.
Before it writes, the service refuses on any of these and leaves the work for your call with the reason recorded:
- The automation is not running, or the person who created it is no longer an editor
- The brand has no paid access
- The target is not a page the brand owns
- There is no before snapshot, or the platform cannot revert that fix type
- The weekly limit for that area is full
- Automatic revert is not armed, or the quality check has tripped
Where the settings live
The automation record at /automations is the editor, under How far it can go. Only a brand editor can change it; a viewer can read the record, and client portal users cannot.
The Agent workspace drawer's Approvals tab is the brand-wide view. It rolls every automation into one row per area, says Mixed when they disagree rather than picking a winner, and shows the reason when a rung is not available instead of greying out in silence.
To stop work quickly, pause the automation from its row menu in Automations, then lower the rung. New checks will not start while it is paused, and a check that already started may finish under the permissions it read when it began.
Limits that do not change
- Getting listed stops at Prepare drafts. The Agent drafts outreach; a person sends it.
- Community replies stops at Prepare drafts. The Agent drafts a reply; a person posts it.
- An automation cannot raise its own rung, widen its scope, or increase its weekly limit.
- Site changes above Prepare drafts need a before snapshot and a supported revert path.
- Text fetched from a page is data, never an instruction the Agent will follow.
No plan and no setting turns outreach or community replies into automatic sends. That cap is a product decision, not a rollout stage.
Common questions
How do I see what it did?
Open the automation record and read its checks. Applied site changes also appear in Actions and in the site's change history with the old and new values, and the later measurement shows up as that Action's result.
How do I take permission back?
Open the automation record, expand the work area, choose a lower rung and save. Lowering never asks for a confirmation. Pause the automation first if you need new checks to stop immediately.
Does every teammate need their own permission?
No. The grant belongs to the automation, not to a person, and the automation then acts for the brand under it. Only a brand editor can raise, lower, pause or resume it.
What happens to work already in flight?
The lower rung applies from the next check. A check that already claimed its work may finish under the permission it read at the start. Drafts already prepared stay available for review, and applied changes stay in history until you revert them.
Can everything be stopped at once?
Trakkr operates a service-wide switch that halts every agent tick and every mutation, but it is not an account setting. On your side, pausing each automation from the register is the equivalent control.