Approvals

zv1 doesn't just talk — it can do things: draft a flow, edit one, add pages to a Compass map. That's most of its value. But an assistant that changes your workspace on its own is one you can't fully trust. So out of the box, zv1 proposes and you decide.

How it works

When zv1 wants to make a change — anything that would change your workspace — it shows you an approval card right in the chat: exactly what it's about to do, before it does it. You Approve or Deny.

• Approve — zv1 makes the change and carries on from there.
• Deny — nothing happens, and zv1 adjusts course based on what you tell it.

Reading things — listing your flows, looking at an eval, searching your map — needs no approval; those don't change anything.

If you'd rather not be asked

The approval step is yours to keep or drop. In your account settings, Require approval for agent writes is on by default; the same switch sits at the top of the chat panel, reading Asks first or Auto-approve. Turn it off and zv1 makes changes immediately instead of showing you a card first.

The setting is per person. Turning it off for yourself doesn't change what anyone else on your team sees, and it doesn't widen what zv1 is allowed to reach — only whether it pauses on the way.

Servers you've connected

A connected MCP server brings its own tools, and you choose how zv1 may use each one:

• Ask — every call to that server waits for your approval, reads included.
• Auto-reads — anything that only looks things up runs without asking; anything that changes something waits.

So a read can require approval after all, if it's a read on a server you've set to Ask.

What you can rely on

With approvals on, zv1 can build alongside you without anything reaching your workspace you didn't see and okay first. Propose, review, approve — the way you'd work with a careful teammate.