Controls
Choose when Proto asks before acting
Set the review behavior for your work and understand the additional controls around ERP.AI deletion and access changes.
Proto can prepare work and perform actions. Choose the approval behavior before you give it a task involving messages, payments, bulk updates, or other consequential changes.
Set the permission mode
Open Settings → Permissions → Uninterrupted mode.
| Setting | What it means |
|---|---|
| On | Proto chooses recommended options and runs confirmable actions without questions or review prompts. This is the default for new installs. |
| Off | Proto asks questions and requests review when an action needs your input. Bulk ERP.AI changes and risky browser actions can require approval. |
Uninterrupted mode does not supply missing credentials, override an ERP.AI account’s access, or grant operating-system permissions. Hard safety blocks still apply.
Turning it off is useful when you want to inspect proposed actions as you work. It is not a promise that every read or every individual operation will produce a separate dialog.
Plan mode is a planning aid, not a read-only sandbox. It can run actions without prompts; leave Plan mode when the task requires action review.
Understand the separate ERP.AI controls
Open Settings → Security to review the ERP•AI actions settings.
| Control | Scope |
|---|---|
| Allow sensitive ERP•AI actions | Roles, user access, and invitations. Bulk record updates follow the normal permission mode. |
| Allow ERP•AI deletion | Deletion of ERP.AI resources, including bulk deletion. The permission mode and account access still apply. |
Both controls are off by default. Enable one only when the intended task requires it and your account is authorized to perform that work. A setting in Proto cannot give you rights that the connected ERP.AI account does not have.
Make the stopping point explicit
For preparation work, say what should be produced and what should wait:
Review overdue invoices and draft reminder messages. Show me the recipients, amounts, and message text before sending anything.
For an app or workflow, specify the desired state:
Build this as a draft. Show me the fields, test result, and proposed trigger before activation.
A workflow may be activated after its test passes when activation is part of the requested work. If you want a draft, include that in the request.
Review the outcome after approval
Approval authorizes an attempt. Check the recorded action and the destination system to confirm what happened. A drafted message is different from a sent message; a saved workflow is different from an active workflow with a successful run.
If a send, payment, or write ends with an uncertain result, first ask Proto to inspect the destination and reconcile the original attempt. Repeating the action immediately can create a duplicate.
Other desktop apps use the separate, experimental Computer Use capability. Enabling it and granting system permissions is distinct from approving a particular business action.