> 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/how-to-exclude-ooo-reviewers.md). # How to Exclude OOO Reviewers Learn how to exclude out of office users from being automatically assigned as reviewers. FlexReview allows users to mark their out of office dates in Aviator to prevent them getting auto assigned when they're away. This helps reduce the load on their teammates who no longer have to keep an eye out of stray reviews and also helps the PR creators not have to chase down an unavailable user. ## Setting you or a teammate's out of office dates Navigate to the Settings -> Out of Office page in your Personal settings. If you've noticed a teammate forgot to set their own OOO, you can navigate to their Github user in the top right corner. Then fill in the form with the start and end dates for the out of office event, and optionally leave the reason so your teammates know where you are.

--- # 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/how-to-exclude-ooo-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.