Menu

Letting an AI near client files: the approval gate we built first
📰

Letting an AI near client files: the approval gate we built first

DEV Community: security·Fedix·3 days ago
#v60ZW4Jt
#devtosecurity#devto#dev#fedix#feature
Reading 0:00
15s threshold

If you have ever watched an AI tool confidently rewrite something it should have asked about first, you already know the real question for a practice: not "can it do the work?" but "who signs off on the change?"

We build Fedix and MYLEDGER for Australian accountants, and we made that question the first design decision rather than the last. This post walks through the guardrails we think any AI assistant near client records should have, and how ours behave. It is general information about our software, not advice about your obligations.

1. Nothing changes until a person says so

The basic pattern is a gate. When the MYLEDGER Copilot or a connected assistant asks for a change, that change waits for a person to approve or reject it. The AI proposes; your team decides. [feature:acb-copilot-write-gating]

The same idea applies to Xero. Every change Fedix would make in Xero is confirmed by a person in a confirmation dialog first.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.