Needs You

Needs You is the inbox of the Regent workspace: one list of everything a person has to decide before the team can carry on. Proposed changes from Proposed Changes, questions a job stopped to ask, permission and secret cards, sign-ins a browser role is stuck on, and jobs that failed in the last week all land here, grouped by kind, and each row carries its own action so you never have to open the run to deal with it.

Key capabilities

• One queue, five kinds — filter pills for All, Proposed changes, Questions, Permissions, Sign-ins and Failed jobs; the All view shows every non-empty group in that order, newest first within each
• Decide in the row — Approve or Reject a proposed change (a rejection needs a reason the teammate learns from), type an answer to a question or pick one of its options, Allow / Allow always / Deny a permission card, save a login or enter a one-time code for a sign-in, and Run again a failed job with the same brief
• Who asked, and where — every row names the teammate, says how long it has waited, and opens the job's post in Team chat (or the run drawer when it has no post)
• Every client at once — in a firm, switch from This business to All my businesses to review the whole book of clients from one place; rows then name the business too
• The badge is the count — the number on the Needs you tab in the Regent header, the Regent rail item and the Agents need you tile on the Daily Brief all read the same total, so clearing the queue clears them
• Stays current — the list refreshes on its own while the tab is open, when you come back to it, and the moment something is decided anywhere else (Team chat, the run drawer, Proposed Changes)

How it works

Every job a teammate runs can stop for one of five reasons. A gated write becomes a proposed change and waits for approval. A question or a card (permission, secret, sign-in) parks the run in Needs you until someone answers. A failure ends the run with a reason. DayZero counts all of these per business in one call and shows them here; the same call feeds the header badge and the Daily Brief tile. Answering a row signals the run, which resumes from where it stopped, and the row leaves the queue on the next refresh.

flowchart LR
  job["Job stops"] --> kind{"Why?"}
  kind -->|"Gated write"| change["Proposed change"]
  kind -->|"Needs a person"| card["Question, permission, secret or sign-in"]
  kind -->|"Error"| failed["Failed job"]
  change --> queue["Needs you"]
  card --> queue
  failed --> queue
  queue -->|"Approve, answer, allow, run again"| resume["Job resumes"]

How to use it

1. Open Needs you in the Regent workspace header, or click the badge on the Regent rail or the Open Needs you link on the Daily Brief tile.
2. Leave the filter on All to work top to bottom, or pick a kind to clear one group at a time.
3. On a proposed change, read the summary, tier and amount, then Approve or Reject; a destructive change asks you to confirm. Open in Books shows the full diff.
4. On a question, click one of the offered options or type an answer and press Answer (or Ctrl+Enter). The job picks up from your reply.
5. On a permission card, read the tool and command, then Allow, Allow always (remembered for the rest of the run) or Deny. Only the person who started the job or an admin can allow a tool; the card says so for everyone else.
6. On a sign-in card, save a login for the site, enter a one-time code, or confirm I signed in once you have done it yourself.
7. On a failed job, read what went wrong and click Run again to hand the same brief to the same teammate, or Open to read the transcript first.
8. In a firm, switch to All my businesses to review every client's queue at once.

Pro tips

• Start the day here: an answered question or an allowed tool resumes its job at once, so the team finishes its work before you sit down to Proposed Changes.
• Permission cards you cannot allow are not yours to worry about: the card names who can, and that person already has a notification.
• A failed job older than a week drops off the queue on its own; it stays in Agent Runs under Failed if you still want it.
• The same queue reaches you in Slack when the Team chat mirror is on, with the same actions.

In-depth guide

What counts

A card whose run already finished waits on nobody and is not shown. The badge total counts every group once; a sign-in is one card, not two.

Who can act

Anyone who can make changes on the business can approve a change, answer a question, finish a sign-in or hand over a secret. A permission card stays with the person who started the job, a business admin or DayZero staff; other readers see the card with its controls greyed out and a line saying who can allow it.