Set autonomy and approval boundaries
Choose whether Edvin should recommend, work internally, or operate, while keeping sensitive and external actions under explicit control.
Updated Jul 13, 2026
What you will have
Outcome
A clear boundary between what Edvin may do independently and what still requires a person to approve it.
Choose the simplest autonomy level
Recommend keeps Edvin read-only and advisory. Work internally allows drafts and internal deliverables. Operate allows configured actions only within workspace policy and the assignment's narrower permissions.
Name approval requirements
Call out actions that need approval, such as an external email, a customer-facing commitment, or final publication. High-impact external actions use an exact preview so the approver can see what will happen.
Change the boundary explicitly
An assignment may be narrowed at any time. Expanding its authority requires an explicit workspace or assignment change; Edvin does not infer broader permission from a casual reply.
Try it in chat
Use this as a starting point. Add your real goal, source material, and deadline.
“Work internally on this launch plan. You may research and create files, but ask before sending anything externally.”
More ways to ask
“Recommend a response, but do not create or send anything.”
“Draft the customer update and prepare the attachment. I will approve the send.”
“Operate within our approved support policy, but escalate refunds and commitments.”
Things worth knowing
- Use Work internally as the safe default for new assignments.
- Approval applies to the exact proposed action, not a blank permission.
- Connected tools do not automatically grant every action in those tools.
Still blocked?
Tell us where the guide stopped being useful.