> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/requests/track-and-organize-requests.md). # Track and organize requests Find requests by status, search, tags and date, and archive, trash or restore them one at a time or in bulk. Your dashboard lists every request you can see, newest activity first. Requests with new uploads or comments you haven't opened are shown in bold until you open them. ## Request statuses | Status | Meaning | | ------------- | -------------------------------------------------------------------------------------------------------------------- | | **Draft** | Not sent yet. Only you can see your drafts. | | **Sent** | Sent and waiting on the recipient. Reminders go out on schedule. | | **Responded** | The recipient has uploaded something to an open-ended request, or responded to every checklist item. Reminders stop. | | **Expired** | The expiration date passed while the request was still **Sent**. Reminders stop. | | **Completed** | You marked it complete. The recipient can no longer upload. | | **Archived** | You archived it. The upload link is disabled. | A request in the trash keeps its status but isn't listed with the others. See [Expiration, completion and reopening](/requests/expiration-and-reopening.md) for how requests move between statuses. ```mermaid flowchart LR Draft --> Sent Sent --> Responded Sent --> Expired Expired --> Responded Responded --> Completed Sent --> Completed Expired --> Completed Sent --> Archived Responded --> Archived Expired --> Archived Completed --> Archived Expired -. reopen .-> Sent Completed -. reopen .-> Sent Archived -. reopen .-> Sent ``` ## Browse by status The left sidebar has shortcuts: * **Inbox**: requests that are **Sent** or **Responded**. This is your dashboard's home. * **All Requests**: everything, with sub-views for **Drafts**, **Sent**, **Responded**, **Expired**, **Completed**, **Archived** and **Trash**. Each row shows the recipients, subject, progress and created date. Hover over a request's progress to see a breakdown. ## Search, filter and sort * **Search requests** (top of the page) matches a recipient's name, email or phone number, the subject, a tag, or the name or email of the teammate who sent it. * **Filter Requests** opens filters: * **Unread Requests**: only requests with activity you haven't opened. * **My Requests**: only requests you sent or are assigned to. Shown to team members who can see their teammates' requests. * **Filter Tags**: pick one or more tags. * **Filter by date** limits the list to requests created in a range. Pick a preset such as **Last 7 days**, **Quarter to date** or **All time**, or choose your own dates. ## Tags Tags are labels you choose, such as "Onboarding" or "2026 returns". Add them under **Tags (Optional)** when you create or edit a request, or set them on a template so every request sent from it is tagged. Then use **Filter Tags** or search to pull those requests together. ## Archive, trash and restore On a request's page, use the toolbar icons: * **Archive request** disables the upload link and moves the request to **Archived**. Use it for finished work you want to keep out of your Inbox. You can reopen it later. * **Delete request** moves the request to **Trash**. Recipients can no longer open it. Requests stay in the trash until you restore or permanently delete them. * In the trash, open the request and use **More options** > **Restore request** to bring it back, or **Permanently delete** to remove it. A permanently deleted request can't be restored. ## Bulk actions Tick the checkbox next to each request, or tick the box in the header to select every request on the page. Hold Shift while ticking to select a range. Once a page is selected, you can **Select all** matching requests across every page. With requests selected, use **Archive Requests** or **Delete Requests** (move to trash). In **Trash**, the options are **Restore Requests** and **Delete Requests** (permanent). Bulk actions ask you to confirm before they run. ## Mark a request unread On a request's page, click **Mark unread** to flag it for later. It shows in bold and under **Unread Requests** until you open it again. ## Related * [Assign requests to teammates](/requests/assign-requests.md) * [Reports](/team-and-account/reports.md) * [Understanding reviews](/reviewing-and-exporting/understanding-reviews.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.pipefile.com/requests/track-and-organize-requests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.