> 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/excluding-reviewers.md). # How to Exclude Reviewers Learn how to exclude certain reviewers from being suggested. They will be still accepted for approval check validation but are never suggested by FlexReview. In a large organization, it may be desired to exclude certain reviewers from being suggested. These could be SREs, managers, product managers, designers or other inactive collaborators who may have access to the code base, and have contributed in the past but are passive collaborators now. The excluded reviewers are still accepted for approval check validation, but are never suggested by FlexReview. To exclude the reviewers, go to [Repositories list view](https://app.aviator.co/repos), search for the repository that you want to change, and select FlexReview Status > Configure.

On this page, enter their GitHub handles on the FlexReview config page. Enter one username per line.

For situations where you want reviewers not to just be excluded from automated reviewer suggestion but to be completely ignored by FlexReview, you can add them to the Ignore List. This is ideal for bot users that are set as a normal User account in GitHub. On the same page as the Reviewer Exclusion you can open up the Ignore List and add one GitHub username per line:

--- # 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/excluding-reviewers.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.