Reads are immediate. Writes wait for approval.

Ask questions and read authorised Xero data straight away. When an assistant proposes a change, Invio places it in a queue for a person to review before it is executed.

Reads do not enter the queue

Report, invoice, receivables and payroll read tools fetch information when the assistant calls them. You do not approve each question. The organisations and permission groups available to a connector depend on what was authorised.

A write starts as a pending change

Write tools save a proposed change in Invio's pending-change store. A person with approval rights can review it and approve or reject it. Pending changes expire after 24 hours, and the account has a limit of 100 open changes. An unapproved proposal is not sent to Xero.

Approve only after reviewing the proposal

Owners and Approvers can act on changes. Chat approval requires an explicit instruction and a confirmation value; an assistant must not infer consent. Viewers have read-only access and do not receive write or approval tools. Organisation restrictions can limit a team member to assigned organisations.

Check payroll proposals with care

Payroll writes follow the same approval queue, subject to the region-specific capabilities. For example, a pay run can be created in Australia and New Zealand, while posting is available only in Australia. See the payroll details and more examples of connector tasks.

Questions we get asked

Do I approve every read?
No. Reads run when requested. Approval applies to proposed writes.
How long does a proposal stay open?
A pending change expires after 24 hours if it has not been resolved.
Can a Viewer create or approve changes?
No. Viewer tokens are read-only and do not receive write or approval tools.
Can an assistant approve its own proposal?
Approval requires an explicit human instruction. The approval tool requires confirmation and the assistant is instructed not to infer consent.
Xero MCP Connector Approvals | Invio