Docs / For owners
Decide what your assistant may do alone
Pick a trust level for each conversation, save okays your assistant can reuse, and decide what waits for you.
Checked against the product on 8 Nov 2026
What this page states, and how each is checked
- A new conversation starts on Ask once.Setting in the code
- On Safe a request waits for the owner even when it names an okay, and the okay is paused.Automated test
- On Ask once, a request that names no okay waits for the owner.Automated test
- On Full handoff a change goes ahead at once, while money, deleting and anything outside the project wait for the owner.Automated test
- With the go-live switch off, going live waits for the owner, on Full handoff too.Automated test
- The switch that lets go-live go ahead is off by default and only the owner can turn it on.Automated test
- The assistant can lower the trust level but cannot raise it.Automated test
- An okay for changes does not approve going live, and no okay approves money.Automated test
- An okay the assistant saves covers nothing until the owner confirms it.Automated test
- Marking a conversation done keeps its okays, and they still cover once it moves on.Automated test
- The owner can approve a request, approve it and save an okay that the next similar request uses, or decline it with a note.Automated test
- Saving an okay for similar requests is refused for money, deleting and anything outside the project, and when the request's own words ask for one of those.Automated test
- The request card shows no "Approve, and allow" button for money, deleting and anything outside the project, or when the request's own words ask for one of those.Setting in the code
- A guest's change request is refused on Safe and when the Change requests add-on is off.Automated test
- On Full handoff a guest's request waits on arrival; once the assistant says what kind it is, money waits for the owner and a change is approved.Automated test
- A guest's change request is 3 to 500 characters, with an optional page name of up to 200 characters.Setting in the code
- The owner gets at most one "Allow it?" email per conversation per 10 minutes.Setting in the code
- A guest approval can be allowed Once, Twice, 3 times or Until you remove it.Setting in the code
- With the go-live switch on, the assistant's go-live ask is approved and the owner is emailed after, on Full handoff too.Automated test
- An approval the assistant sets is not offered to the guest until the owner confirms it.Automated test
- Guest text such as "approved" records no approval and creates no okay.Automated test
- Money, deleting and anything outside the project wait for the owner on Safe, Ask once and Full handoff, even when the request names an okay.Automated test
- The trust level is picked under Who can do what.On-screen text
- Saved okays are listed behind See and revoke.On-screen text
- The owner saves an okay with the Add okay button.On-screen text
- The guest asks for a change with the Ask for a change button.On-screen text
- Guest approvals is an add-on the owner switches on.On-screen text
Automated test: a test in the product must pass. On-screen text: the words must exist in the product. Setting in the code: the number is read from the code. The docs are published only when every check passes.
Tested with Claude only
Each conversation's trust level sets what your assistant may do without you. Anything it may not do alone waits in your inbox until you approve or decline it.
Pick a trust level
- Open the conversation and open Who can do what.
- Pick Safe, Ask once or Full handoff.
- Safe: every action waits for you, and your saved okays are paused.
- Ask once: where a new conversation starts. An action waits for you unless your assistant names an okay you gave.
- Full handoff: changes inside the project go ahead at once.
Your assistant can lower the level but never raise it.
What Full handoff does not cover
Money, deleting and anything outside the project always wait for you, at every level. Going live also waits. To let it go ahead, turn on Deploys and go-live don't need me for that conversation; it is off until you do, and your assistant cannot turn it on.
Save an okay
An okay is a yes your assistant may reuse for one kind of action. An okay for changes does not approve going live, and no okay approves money.
- Under Who can do what, tap See and revoke (or Add one).
- Write what it covers and tap Add okay.
An okay your assistant saves from your chat covers nothing until you allow it. Marking the conversation done keeps its okays.
Decide a request
A waiting request offers:
- Approve says yes to this one only.
- The button starting "Approve, and allow" also saves an okay. Edit the words under From now on, allow and tap Approve and save. It is not offered for money, deleting or work outside the project, or when the request itself asks for one of those.
- Say no declines, with an optional note for the guest.
Change requests from guests
With the Change requests add-on on, the guest gets an Ask for a change button. Requests are refused on Safe. A request is 3 to 500 characters, plus an optional page name of up to 200. It never goes ahead on arrival, even on Full handoff: your assistant first says what kind it is, and then the rules above apply.
Let a guest approve something
Switch on Guest approvals under Add-ons, name one thing the guest may approve with a button, and choose Once, Twice, 3 times or Until you remove it. Typing "approved" in the chat never counts. Anything your assistant suggests for the guest to approve waits until you allow it. Two Cans can email you about it, at most once per conversation every 10 minutes.
Replies can also wait for other reasons: see Keep each conversation to its own project.
Guests can add background work too: see Run background work as tasks.