Reviewing drafts

Review a request

1. Open Review in your workspace; pending requests are under Needs review.
2. Open a request to see exactly what would change, field by field, along with the agent's summary and any reasoning it included. A risk level appears when it's above low, and the full requested action and the Policy snapshot — a record of the safety checks Noeryx applied when the request was created — are under Technical details.
3. Approve to apply the change, or Reject to discard it. For a pending request, these buttons sit right on its row in the list and on the request's full-details page.

You see and decide on requests from your own agents. Owners and Media Buyers follow the same personal boundary: another member's requests, chats and history remain private, including through direct links. The library view selector does not change your review queue.

Calendar tasks with Auto-approve agent actions enabled can approve eligible requests automatically. Their decisions appear in History as Auto-approved. Any request that the automatic policy does not allow still needs your decision.

Decide right in the chat

When an agent proposes a change in a chat, the same request also appears inline as an approval card in the conversation, with Approve and Reject and a link to the full details. You can decide there without leaving the chat — the card shows the live status and stays in the conversation when you reload. It's the same approval as on the Review page, so deciding in either place does the same thing.

What happens after you approve

Your decision and the work of applying it are tracked separately:

• The decision (approved/rejected) is recorded immediately.
• The apply runs as a background task and reports its own status: queued, running, succeeded, or failed.

If applying fails after approval, the request stays approved and shows a failed apply state you can retry safely with Retry apply — you don't re-approve. After a successful apply, Noeryx refreshes the affected records so your campaign view reflects the change.

See what happened to a request

Every request has a short History under its details. It lists each step once, oldest first, with its date and time when Noeryx records one:

• Requested — the agent that proposed the change, and whether it came from a Calendar task.
• The decision — Approved, Rejected, Auto-approved, Expired, or Canceled — with who made it. An approval or rejection also shows the note the person added, if any, and a cancellation says why Noeryx canceled the request.
• Apply queued, Apply started, and Applied as the change goes through. When applying doesn't finish, Apply failed follows, or Apply stopped when Noeryx can't tell whether the platform made the change; these two have no time, and the notice above the History explains what to do. After Retry apply, these steps show the latest try.
• Archived — who archived the request.

Your own steps show you. A Calendar task that approves a change by itself shows Calendar automation. Steps Noeryx takes on its own, such as expiring a request nobody decided in time, show Noeryx. Someone who has left the workspace is marked Former member, and a blocked member Blocked.

The request and its History are visible only to its own member. Workspace administration does not grant access to another member's approval history.