Skip to content

Agent Controls

Regent → Controls lists everything that can act on a business without a person at the keyboard: the agent roles on your team, the connected apps that reach DayZero over MCP, and partner API clients. For each one you see what it may do, which payment mandates it holds, how much it has paid this period against its ceiling, and its most recent actions.

Who appears

  • Agent roles — each teammate on Regent → Team, with its scope (read, or propose changes) and tool access.
  • Connected apps — every MCP client a member has connected, with the scopes they granted and when it was last used.
  • API clients — partner integrations signing in with their own keys, with their scopes and last token use.

Payment mandates

By default an agent never pays a vendor on its own: a bill payment it wants becomes a proposed change for a person to approve. A payment mandate lets one agent, app or API client pay within limits you set:

  • Vendors it may pay (or any vendor).
  • Per-payment ceiling and a period ceiling per month or week.
  • Valid from / to dates.

A mandate takes effect only after two people have agreed: one proposes it, and a different owner or admin counter-signs it. If you are the only admin of the business you can self-sign, and that choice is recorded on the mandate and in the audit log. Revoking a mandate stops agent payments under it at once.

A payment that fits an active mandate goes through without an approval card. A payment that does not — wrong vendor, over the per-payment ceiling, period ceiling used up, mandate expired or revoked — is filed as a proposed change as before, and the proposal says which rule it failed.

What a mandate is and is not

A mandate is DayZero's own authorization record. It governs what DayZero lets an agent record and initiate in your books. It does not by itself satisfy a bank's or a card network's authorization rules for moving money: your bank connection, card program and payment provider keep their own controls.

Verifying a mandate

Every counter-signed mandate carries a signature. Journal entries created under a mandate show a Mandate badge; open it to see the role, the ceiling, who approved it, and a Verify link. The verifier confirms the signature matches the stored mandate and shows only a ceiling band — never amounts, vendors or names. You can also export a mandate in an AP2-shaped format for agent frameworks that carry payment mandates; nothing is sent anywhere when you do.

Locked periods are enforced for agents

Closed and locked accounting periods stay closed for everything that is not a person. An agent role, a connected app or an API client that tries to post, edit, delete or re-categorize something dated in a closed period is refused, and so is a chart-of-accounts change that would rewrite closed history, such as merging two accounts or changing an account's type. The refusal names the period, and only a person can reopen it.

The card at the top of Controls counts the attempts DayZero blocked in the last 30 days. Every attempt is also recorded with who tried, what they tried and which period stopped it, so a blocked write is a line you can read, not a silent failure.

Timeline

The Timeline tab is one log for every actor. It merges what agent roles did in their runs, changes that apps and agents proposed, the approvals and declines people gave, automation runs (and their undo), payments made under a mandate, apps that were connected or revoked, and the blocked closed-period attempts, newest first.

  • Filter by actor type and by a single actor, and narrow what is loaded with the outcome chips: done, blocked, waiting or declined.
  • Each row opens the run, the proposed change, the journal entry or the mandate it is about. A blocked attempt shows a lock and says why.
  • A proposed change from a connected app or API client shows the kind of client but not which one: DayZero does not record that on the proposal.

Pausing and revoking

The buttons on each card call the controls you already have: Pause a role (Regent → Team), Revoke a connected app (Settings → Connected accounts), Disable an API client. Mandates for a paused or revoked subject stay listed so the record is complete.

Asking Regent

  • "Which agents can pay bills?" — Regent reads the same page.
  • "What did the agents do this week?" or "Did anything try to edit closed books?" — Regent reads the Timeline.
  • "Let the AP agent pay bills up to $2,000 each, $10,000 a month" — Regent proposes the mandate after you approve; another admin counter-signs it.