> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/assign-vulnerabilities-to-team-member.md).

# Assign vulnerabilities to team member

How to assign Snyk API and Web vulnerabilities to a team member

You can assign a vulnerability to one of your team members from several places: the **Target** page, **Scan Results** page, or **Finding Details** page. Assigning vulnerabilities helps track responsibility and ensures that the appropriate team member addresses each vulnerability.

## Assign from Target or Scan Results page

You can assign findings in bulk to a user from the **Target** page or **Scan Results** page.

1. Select one or more vulnerabilities by selecting the respective check boxes on the left-hand side.
2. A dropdown menu appears so you can assign the vulnerability to one of your team members.
3. Click the dropdown, select the teammate to assign the vulnerabilities to, and confirm the action.

## Assign from Finding Details page

You can also assign a vulnerability to a team member directly from the **Finding Details** page.

1. Access the **Finding Details** page.
2. Click the **Assign** dropdown to choose the user.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/assign-vulnerabilities-to-team-member.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.