Agent features: learn from feedback, permission roles and approvals

Learn from feedback

• What it notices: someone rewrites a large part of a draft an agent made (35% by default; you can choose 20–70%), or deletes it instead of publishing. It covers articles and landing pages published from Content Studio, social posts edited or deleted in Broadcast, and anything edited by hand in the desktop app’s Studio panel.
• What you see: the draft appears under Feedback to learn from with what the agent wrote, what you kept, and a rule an AI suggests from the change ("Write in British English", "Never promise delivery dates").
• What you do: say why if you like, adjust the rule, and save it as a brand rule (guidance agents follow), a banned phrase (added as a warning, so it never blocks by surprise) or an approved claim. Or dismiss it.
• Agents ask too: the desktop agent, the Reaudit assistant and Claude or ChatGPT over MCP see open feedback when they start writing for the project, ask you in one line why, and save your answer. They never guess your reason.

Agent permission roles

• Set a level for each kind of agent: the desktop agent, the Reaudit assistant, MCP clients (Claude, ChatGPT…) and API keys.
• Everything: no limits (the default).
• Drafts only: the agent can write and edit drafts, check them and read data, but cannot publish, schedule, cross-post, open SEO pull requests, submit URLs to Bing or change live ad accounts (switching campaigns on, bids, negative keywords, new ads). A WordPress draft is still allowed.
• Read only: the agent can read and check, but not change anything.
• Refused actions are listed in Agent activity as blocked, with the reason, and the agent is told to leave its work as a draft for a person to publish. Your own edits in the desktop Studio panel are never limited.

Approval chain

• Steps: by default Brief → Copy → Creative → Legal → Launch. Rename, reorder, add or remove steps, and choose each step’s owners (none chosen = any project owner or admin).
• Submitting: agents submit their drafts (articles, landing pages, social posts, ad campaigns) themselves; people use Submit for approval in Content Studio or the desktop app’s Studio panel and schedule dialog. The owners of the first step are notified.
• Deciding: open Approvals (from the notification, or /dashboard/approvals; in the desktop app Settings → Approvals). Approve the step, or request changes with a comment. Each approval notifies the next step’s owners; the last one marks it approved. Agents can never approve.
• Publishing: agents cannot publish, schedule, cross-post or switch on an ad campaign until it is approved. Turn on Hold people’s publishing too to make Content Studio, Broadcast and ad publishing wait as well.
• Edits: what is approved is exactly what was submitted. Editing an item during review blocks the approval until it is resubmitted, and editing it after approval needs approval again.