Skip to content
Open appSchedule a pilot

Proposed Changes

Proposed Changes is your approval inbox for writes that an agent previewed and queued instead of applying. Each one shows exactly which values would change, so you can approve with confidence or reject it with a reason. Your books stay untouched until you decide.

Key capabilities

  • One inbox for changes proposed by Regent, AI tools connected through Connect AI Assistants, API clients, and workflows
  • A before-and-after table for every change: record, field, old value to new value, and the amount when money is involved
  • A tier badge on every change (Rule, Review, or Approve individually) that tells you how it is meant to be approved, with the reasons on hover
  • A Destructive badge on anything that deletes, voids, or cancels records
  • Approval rounds: an agent batches many changes (for example a month-end cleanup) and you approve all except the ones you pick
  • Protection against stale previews: if your books changed after the preview, nothing is applied
  • A waiting count on the sidebar link and the Waiting filter, plus a notification that links straight to the change
  • Approved changes run as you, with your access, and are recorded in the Audit Log

How it works

An agent previews a write, then queues it here instead of applying it. Owners and admins are notified. A person with the right access approves it and DayZero applies it. If nobody decides within seven days it expires.

flowchart LR
  prop["Agent proposes a change"] --> wait["Waiting for approval"]
  wait -->|"Approve"| apply["Applying"]
  apply --> applied["Applied"]
  apply --> failed["Failed"]
  wait -->|"Reject"| rejected["Rejected"]
  wait -->|"7 days pass"| expired["Expired"]

Each change gets a badge when it is proposed, based on what it would do, not on how sure the agent is:

Badge What lands here How it is approved
Approve individually Chart-of-accounts and counterparty merges or structure changes, period close, lock, reopen and sign-off, reversals and voids, equity, payroll, tax and loan accounts, anything that deletes, voids or cancels, anything dated in a closed period, and any change at or above your materiality One at a time. Never included in a round approval
Review Everything else Singly, or in a round with Approve all except
Rule Rule-shaped changes under materiality: bank rules, counterparty defaults and naming rules, recorded decisions Approved once; the rule then applies itself

Materiality is $5,000 unless an owner or admin sets another amount (see Approval settings below).

How to use it

  1. Open Proposed changes in the sidebar, or click the notification you received. The linked change is highlighted even if another filter is active.
  2. Read the header of each card: the summary, the action name, who proposed it, whether it came through a connected AI tool, the API, Regent, or a workflow, and how long ago.
  3. Check the table of changes. If it is cut short ("Showing 20 of 140 changes"), click Show all. Open Exact arguments to see the precise values the change will run with.
  4. Click Approve to apply it or Reject to close it without changing anything.
  5. In the confirmation window, add a note (optional when approving) and click Approve and apply, or give a reason (required, at least 3 characters) and click Reject.
  6. Use the filter buttons (Waiting, Applied, Rejected, Failed, All) to review past decisions. Click Load more for older items.

Approving a round

When an agent submits a round, it appears as its own card on the Waiting filter, with its waiting changes listed by dollar impact, largest first.

  1. Untick any change you want to decide separately. Approve individually changes have a locked, unticked box and always stay waiting; use the Approve and Reject buttons on their row.
  2. Click Approve all except, add an optional note, and confirm. Each change is applied on its own, as you; one that fails is reported and the rest carry on.
  3. Or click Reject round, give a reason, and every waiting change in the round is closed.

A round that the agent has not submitted yet shows as Being prepared. A submitted round shows Waiting for you and expires in seven days.

Approval settings

Owners and admins see an Approval settings button at the top of the page.

Setting What it does
Materiality A change at or above this amount is approved one at a time. Leave it empty for the $5,000 default
Deputy approver Someone who can approve here and is reminded, along with the owner and admins, when a round has waited two days

What each status means

Status Meaning
Waiting for approval Proposed and not yet decided
Applying Approved and being applied
Applied The change was saved
Rejected You closed it without applying
Failed Approved, but could not be applied; the card shows why
Expired Not decided within seven days

Applying and Expired items only show under All. Applied, rejected, and failed cards show who decided and when, plus any note.

Who can approve

Approving needs write access to the business, plus delete access for a destructive change, and whatever permissions the underlying action needs. Without them you get an error and the change stays waiting. The approver's identity is what is applied and logged, not the agent's, so a change can never do more than the person approving it is allowed to do. API tokens cannot approve, reject, or change approval settings; a signed-in person must.

Tips and common problems

  • A rejection reason is passed back to the agent that proposed it, so say what you want instead.
  • "The books changed after the agent's preview, so nothing was applied" means the data moved. Ask the agent to preview the change again and propose it fresh.
  • Identical pending proposals (same action and preview) are not duplicated, so repeated requests do not flood the inbox.
  • The Stats filter shows, per action, how many proposals were approved, rejected, or expired and how long decisions take, and per round how long it took to decide. An approval rate near 100% on big rounds decided in seconds can mean rounds are being rubber-stamped; an action approved unchanged every month is a candidate for a standing rule.
  • Click Refresh to reload the list after someone else decides a change.

For agents and developers

AI tools connected through Connect AI Assistants and API clients can queue changes, group them into rounds and read back your decisions. Developers: see the Anomalies and Notifications guide for the API and the connected AI tools guide for the connected-tool side.

Related

In a chat with Regent, ordinary edits use an approval card in the conversation instead. Proposed Changes is for work that waits for a decision later, often from someone other than the person who asked.