You stay in control: sensitive actions wait for a human decision. My Work is the one place that collects everything waiting on you.
My Work starts with In progress: tasks Vori and your employees are working on, their current status and decisions they are waiting for. To-do list contains the shared tasks for people in your company. Proposals are next steps prepared by Vori's team — Approve & run lets the proposing employee start, I'll do it moves it to your to-do list, Dismiss drops it. Recently finished and History show what is done.
Give Vori a task opens Vori. Adding a to-do does not hand work to Vori — Let an employee do it does (a paid run). A band at the top says how many decisions need you and how long the oldest has waited; its links open the exact decision, and Review … together takes a pile of similar ones at once. The full task board, all to-dos, all proposals and History remain available through their links. On detail pages, My work returns to the overview and More views opens the other work views. The sidebar badge counts what needs a human: approvals, questions, proposals, to-dos due today or overdue, and results that could not be verified.

When an employee reaches a sensitive or irreversible action — per your policy — it asks. The run waits for a few minutes (the approval wait, set on the Security page); after that it carries on with the rest of the work and the request stays open — a late approval is still carried out.
Decide wherever you meet it: on Approvals & questions, in the yellow band of a live run, in a 1:1 or team chat, in the follow-up chat, on the Security page, or by asking Vori. Each card offers Approve, Reject (with a reason), Request changes and, for drafted messages, Edit text. A 10-second Undo follows sends, payments, signatures and deletes.
Every approval card reminds you the action was AI-prepared: check content, amounts and recipients before approving. Approving authorises the action — responsibility stays with the approver.
Any member can approve everyday outbound work — an email, a marketing send, a channel post, a CRM write. The actions that move money or can't be undone are owner-only: paying or moving money, writing an accounting record, requesting a legally-binding signature, deleting data, granting admin permissions.
Rejecting is never restricted — any member can stop any action, so nothing dangerous waits on one person.
The approval policy is per workspace, on the Security page: which kinds of action need your approval, the single-payment cap, a recipient allow- and denylist, and the monthly run and spend caps. Per connected tool you set reading and writing separately to Default, Allow, Ask first or Block.
The approval pause is the default, and an owner can relax it — auto-approve records below an amount, monitor mode, standing rules, an employee's earned trust (Allow without asking on its scorecard), per-tool Allow. A per-tool setting never waives the safety guards (secret and personal-data leaks, deletes, untrusted web content), and in every mode, monitor included, leak blocks, the single-payment cap and a human look at irreversible deletes still hold.
