# Answer what needs you > Approve calls, answer questions, and review finished work, drafts and replies in Needs you. **Needs you** is the inbox of what waits on a person. It holds the questions of teammates, the calls that need a yes, the work to review and the drafts to use. Each answer lets a teammate continue. This page tells how to go through it. ## Open Needs you Select **Needs you** in the sidebar. The count beside it says how many things wait on you. On **Home**, the line under the message box says the same, with a rough time to answer them. A list is at the left, and a reading pane shows the item that you pick. When nothing waits, the page says **Nothing waits on you**. ## The groups The list puts the items in 3 groups, in the order to go through them: | Group | What it holds | | --------------------- | ---------------------------------------------------------------------------------------------------------------- | | **Needs your answer** | Questions of teammates, calls that wait for a yes, plans to approve, and lines of the products. | | **To review** | Tasks in **In review**, emails of a campaign to review, tests that the QA tester proposes, and feedback to sort. | | **Ready to use** | Drafts that teammates wrote for you: posts, emails, briefs, copy and articles. | ## Answer a question A teammate asks when it cannot go on without a person. The task waits in **Needs you** until the last answer. 1. Pick the question in the list. 2. Pick one of the answers that the teammate offers, or type **Your answer**. 3. Send the answer. The teammate continues the task. When a teammate asks some questions at one time, the pane shows them one after the other. ## Decide on an approval A call that changes what people rely on waits for a yes: an email, a post, a payment, a rewrite of a doc, a hire. 1. Pick the approval in the list. The pane shows what the call does, with the words or the diff. 2. Select **Approve** to let it go, or **Deny** to turn it down. Only owners and admins decide some calls. Examples are an email from the address of a teammate, a routine that a teammate proposes, and a payment. After the same answer three times in a row, Troopy offers a standing rule: **Always approve** or **Always turn down**. An owner or admin accepts the rule. See [Stay in control of your troop](/docs/control). ## Review finished work A task in **In review** waits for a person to read the result. 1. Pick the task. The pane shows the last answer of the teammate, the pictures that it made, and the docs of the work. 2. Select **Looks good, mark done** when the work is right. 3. Or select **Send back**, and say **What should change?**. The teammate works on the task again. ## Use a draft A draft is a piece that a teammate wrote for you to use: Troopy never sends it. | Kind | What you can do | | -------------------- | ------------------------------------------------------------- | | Post | **Copy text**, then **Mark as posted** when it is out. | | Email | **Copy text**, then **Mark as sent**. | | Article | **Copy title** and copy the text, then **Mark as published**. | | Brief, copy or other | Open it in Docs, then **Mark as used** or **Mark as read**. | A brief, a copy or an article is also a doc in **Docs**, where you can change it. See [Write and share docs](/docs/documents). ## Lines of the products Some products put one line in **Needs you**, with a link to the place where you deal with it: | Line | Where it goes | | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | Emails of a campaign to review, emails that possibly did not go, replies to sort | The campaign, or **Replies**. | | A plan of an engineering ticket to approve, a ticket ready to release, a ticket that stopped | The ticket. | | A place whose scheduled checks fail, tests that the QA tester proposes | **Tests**. | | An app with incidents that need a look | **Incidents**. | | Customers who became at risk, feedback that a teammate sorted | **Customers**. | | A dispute whose evidence waits for a yes | The dispute. Owners and admins only. | | **Still true?** | A note that you said, which teammates rely on. Say if it is still true. | A line of a product shows only to a person who has that product. The two lines of **Customers** have **Mark as seen**. The line goes until there is news: a customer who becomes at risk, or a piece of feedback that a teammate sorts. The line of the feedback also has **Accept all**. It accepts each suggestion of a teammate as it is. ## Who sees what - Owners, admins and members answer, approve and review. - Approvers answer questions, decide approvals and drafts, review emails of a campaign, and sort replies. They move a task that waits on a person to **Done**, or send it back. - Viewers read **Needs you**. Nothing waits on a viewer. - Guests have no **Needs you**. ## Related - [Track work on Tasks and projects](/docs/tasks) - [Stay in control of your troop](/docs/control) - [Choose your notifications](/docs/notifications) - [Invite people and choose their roles](/docs/people)