Route the decision with enough context to make it.
A useful approval is more than a yes/no notification. Voyager can keep the request connected to the work, customer, conversation or schedule context that explains why the decision matters.
CAPABILITY · REQUESTS & APPROVALS
Make decisions and delegated authority part of the workflow.
Many workflows stall because the next step depends on a person making a decision. Voyager treats requests and approvals as first-class coordination objects rather than side conversations.
Use approval as a deliberate boundary between intelligence and action.
Voyager can prepare a recommendation or proposed action, then stop for human approval where policy, risk or preference requires it.
A decision can continue directly into coordinated work.
Once approved, the next steps can remain connected to the same operating context rather than requiring a person to manually recreate the decision in another system.
PRACTICAL ANSWERS
What this capability means in day-to-day work.
Can Voyager require approval before acting?
Yes. The Voyager authority model is explicitly designed to distinguish actions that may run within delegated authority from actions that require approval.
Are approvals separate from the underlying work?
They do not have to be. Requests can remain connected to the work and context that produced them, which reduces the need to reconstruct the decision from separate messages.
Can approvals be used with automated workflows?
Yes. Approval can serve as a control point inside a broader workflow, allowing preparation or coordination to proceed automatically while sensitive actions remain human-controlled.
Start with one bounded responsibility where this capability removes a real handoff, context gap or manual follow-up problem.