Approvals and Needs attention

When an employee needs you, the request is one clear card: approve something, answer something, choose something, or connect something.

Autonomy without checkpoints is how surprises happen. In Verse, an employee that hits something above its pay grade pauses and asks, and every request lands in one queue you can clear in minutes.

The four kinds of request

Kind	What they're asking	You resolve it by
Approve	Permission for a specific action, with a low, medium, or high risk badge.	Approve or Decline.
Reply	Information only you have, like an account number or a decision in words.	Typing an answer and hitting Submit.
Choose	A decision between a few reasonable options.	Picking one and hitting Submit.
Connect	Access to an app the task needs, like Gmail or Notion.	Connect the app, then I've connected it (or Skip).

Where requests show up

In the chat, as an inline card, if you're watching the run live.
On the Runs page, in the Needs action table at the top: who's asking, what's needed, risk, and time left.
On the sidebar, as an amber badge on Runs counting everything pending.

What happens while you're away

The run pauses safely; nothing is retried or forced. Requests expire after about three days by default. An expired request resolves as declined, so the failure mode is always “didn't act,” never “acted without you.” When you resolve a connection request, the employee picks the task back up from where it stopped.

Tip

Seeing the same approval again and again? That's a settings smell. Either raise the employee's autonomy or limits for that action, or tell it in chat how to decide on its own next time.