What are the three autonomy levels in CloudAxis?

Watch only, Ask me first, and Act on its own — set per duty, controlling whether a specialist reports, asks, or acts unattended.

What does approving a held action actually run?

Exactly the action you approved — the same content and recipients — never an expanded or re-planned version of it.

What happens if I never respond to an approval?

It expires and the action is not taken; the specialist does not act on its own just because the approval was ignored.

Do all actions need only a one-tap approval?

No — high-risk actions, like sending to a large list or an irreversible change, require typing a short confirmation code instead of a single tap.

Autonomy & Approvals

Autonomy is a switch on every duty — Watch only, Ask me first, or Act on its own — that controls whether a specialist reports what it would do, asks you before doing it, or goes ahead unattended; a held action always executes exactly as you approved it, nothing else.

The three autonomy levels

Watch only — the specialist observes and reports, but never takes an action that changes anything outside its own workspace. Use this while you're still building trust in a new duty.
Ask me first — the specialist prepares the action and holds it for your approval before anything goes out. This is the default for any duty that can send or publish something on your behalf.
Act on its own — the specialist carries out the action immediately, without waiting for you. Reserve this for duties you've watched run safely for a while.

Set the level per duty in its editor. You decide how much rope each duty gets — a research-heavy duty might run fully on its own, while the one that finally sends the email stays on Ask me first.

Why sending or publishing defaults to Ask me first

Any duty capable of sending an email, posting publicly, messaging someone, or changing a calendar defaults to Ask me first the moment it's created. This is deliberate: actions that leave your workspace and reach another person are exactly the ones worth a second look before they become irreversible.

What "exactly as approved" means

When you approve a held action, CloudAxis runs precisely what was proposed — the same recipients, the same message, the same change. It does not re-plan, expand scope, or take a related action you didn't see. If a specialist wants to do something beyond what you approved, that becomes a new held action with its own approval.

Where to decide

Held actions wait for you in two places, and either one reflects the same decision instantly:

WhatsApp — a one-tap approve or decline, once you've connected WhatsApp; see WhatsApp approvals.
The Approvals inbox — on desktop or phone, a running list of everything waiting on you, with the full proposed action visible before you decide.

Approvals expire

A held action doesn't wait forever. If you ignore it, the approval expires and the action is not taken — the specialist doesn't fall back to acting on its own just because you didn't respond. You can always ask it to prepare the action again later.

High-risk actions require a typed code

Some actions are risky enough that a single tap isn't enough — sending to a large list, an irreversible account change, or anything else flagged as high-risk asks you to type a short confirmation code before it proceeds. This extra step exists specifically to prevent an accidental tap from approving something significant.

Declined actions never run

Declining a held action is final for that instance — it does not run, in whole or in part. If the underlying duty is scheduled or triggered again later, it will propose a fresh action next time, but nothing from a declined attempt ever executes afterward.

Tip: start new duties on Watch only or Ask me first, and only move to Act on its own once you've reviewed several runs and trust the pattern of decisions it's making.