> 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/assign-requests.md).

# Assign requests to teammates

Assign a request to one or more teammates so they get its notifications and handle its review.

On a team, you can assign a request to the teammates who should handle it. Assigned teammates can open the request, get its email notifications, and review what comes in.

{% hint style="info" %}
Assigning needs a team with at least two members. See [Team members and admins](/team-and-account/team-members-and-admins.md).
{% endhint %}

## Assign a request

{% stepper %}
{% step %}

### Open the request

From your dashboard, open the request you want to hand off.
{% endstep %}

{% step %}

### Open Assign

Click **More options** (the **⋯** icon in the request toolbar), then **Assign**.
{% endstep %}

{% step %}

### Pick teammates

In **Assign Team Members**, search by name or email under **Select Team Members**. Choose as many teammates as you need.
{% endstep %}

{% step %}

### Save

Click **Save**. The request page now shows **Assigned to** with their names.
{% endstep %}
{% endstepper %}

To change or remove assignees, open **Assign** again, adjust the list and click **Save**.

## Who you can assign

You can assign anyone the request's owner works with: teammates in the owner's [user groups](/team-and-account/user-groups.md), or the whole team if the owner isn't in a group, plus the team admins. You can include yourself.

## What assigning changes

* **Access:** assigned teammates can open, edit and review the request, even if they couldn't see it before.
* **Notifications go to the assignees instead of the owner.** Uploads, comments, completed checklists and expirations are emailed to the assigned teammates. The owner stops getting these emails unless they also assign themselves.
* **Team admins** still receive copies, as do teammates when your team shares an inbox. Each person controls these copies in their [notification settings](/reminders-and-notifications/notification-settings.md).
* **My Requests:** the request shows up for each assignee when they use **Filter Requests** > **My Requests**.

Recipients don't see who is assigned. Emails to them still come from the request's sender.

{% hint style="success" %}
To hand a request off but stay in the loop, assign both the teammate and yourself.
{% endhint %}

<details>

<summary>I don't see Assign in the menu.</summary>

**Assign** only shows on a team with two or more members, and only on requests that aren't completed, archived or in the trash. Reopen a closed request first. See [Expiration, completion and reopening](/requests/expiration-and-reopening.md).

</details>

## Related

* [Track and organize requests](/requests/track-and-organize-requests.md)
* [Understanding reviews](/reviewing-and-exporting/understanding-reviews.md)
* [User groups](/team-and-account/user-groups.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/assign-requests.md?ask=<question>&goal=<user_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.