> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/flexreview/how-to-guides/whitelist-teams-for-review-assignment.md).

# Whitelist Teams for Review Assignment

Step-by-step guide on whitelisting teams for automatic reviewer assignment in FlexReview.

When [onboarding a large org](/flexreview/onboarding-a-large-org.md), it may be preferred to test out reviewer assignment for a select number of pull requests. There are a couple of ways to do selective reviewer assignment.

### Whitelist by reviewers

To enable FlexReview reviewer assignment for a given GitHub team, go to Teams section in Dashboard, and select the desired team in the dropdown. For this view, click "Enable FlexReview Team".

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FOeFMHcW35gcoeTcyByiz%2FScreenshot%202025-01-07%20at%204.10.32%E2%80%AFPM.png?alt=media&amp;token=27d7ddf8-0dd5-48ee-b0d8-6aef6c39a8c8" alt=""><figcaption><p>Enable FlexReview Team</p></figcaption></figure>

Once enabled, you should be able to navigate to the Team Config and ensure that "Expert Review" is selected for in the Review Assignment section.

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FOz2Xcnb5T6RjexDlKEqq%2FScreenshot%202025-01-07%20at%204.11.58%E2%80%AFPM.png?alt=media&amp;token=5465d85a-32b7-47a6-a929-243d1fe35519" alt=""><figcaption><p>Review Assignment</p></figcaption></figure>

### Whitelist by authors

It may be desired to only assign reviews for the pull requests that are authored by specific users or specific teams. This can be configured at the repository level.

Go to Repositories > FlexReview Status > Configure for the repository that you want to enable this for.

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FHwvySgVxQQ3ZFjZ118fI%2FScreenshot%202025-01-07%20at%203.29.56%E2%80%AFPM.png?alt=media&amp;token=ff39206d-a656-4a60-8ed7-d8a6cbdcd7cc" alt=""><figcaption><p>FlexReview Configure</p></figcaption></figure>

Go to "Author Allowlist". Here you can specify either a user or a team (one per-line) that would be whitelisted for reviewer assignments. Syntax is `@username` for users and `@org/team` for teams. By default all authors are part of the allowlist, this is represented by a special marker `*`.

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FISnjgJ2zwDoDBynQAy1l%2FScreenshot%202025-01-07%20at%204.16.03%E2%80%AFPM.png?alt=media&amp;token=c822770e-4f9f-4496-9d11-33e137ac0beb" alt=""><figcaption><p>Author Allowlist</p></figcaption></figure>

### Working with both

Please note that these whitelists act as AND-gates, that means a pull request will be assigned a reviewer when it satisfies bot the authors and the reviewers whitelists.

## See also

* [Onboarding a large org](/flexreview/onboarding-a-large-org.md)
* [Troubleshooting reviewer assignment](/flexreview/how-to-guides/troubleshoot-reviewer-assignment.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://docs.aviator.co/flexreview/how-to-guides/whitelist-teams-for-review-assignment.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.