Permissions and approvals
A permission lets Milo access a tool or data source. Your instruction describes what you want done with that access. An approval confirms a particular action or decision when the workflow requires it.
These distinctions help you delegate clearly.
State the boundary in the request
| Your intention | Useful wording |
|---|---|
| Explore options | Compare the options and explain the trade-offs. |
| Prepare work | Draft the update for my review. |
| Require review | Ask me before sending or changing the record. |
| Authorize a defined action | Send this approved version to the named recipients. |
Choose the boundary that fits the task. Do not assume that every action will produce a separate confirmation prompt: Milo's behavior depends on the action, instructions and available tools.
Keep business approval separate
A completed task does not remove an organizational approval requirement. Training may be finished while a launch still awaits sign-off. A policy exception may expire even though an earlier invoice followed it.
Include the responsible owner and applicable condition in your request.
Review external actions
Check recipients, destination accounts, amounts, attachments and the exact commitment before authorizing work that affects another system or person. Milo asks for approval before making a payment.
If an outcome is uncertain, inspect the destination before repeating the action. An unclear response does not prove that nothing happened.
For team workflows, agree on which actions can proceed under existing instructions and which need a new decision. Record those boundaries with the process owner during setup.