> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/how-to-guides/workflow/how-to-enable-an-ethics-review-stage.md).

# How to Enable an Ethics Review Stage

1. Select "Yes, our venue has Ethics Chairs and Reviewers" from the venue request form. This can be done when submitting a new support request form, or after your venue has been deployed by using the "Revision" button. This will generate an "Ethics Review Stage" button from the venue request form as well as other necessary customizations.
2. Recruit Ethics Chairs and Ethics Reviewers using the "Recruitment" button from the Venue Request form. 
3. Once you have identified which papers need ethics review, create a comma-separated list of their paper numbers. 
4. From the venue request form, run the "Ethics Review Stage". This will allow you to customize the Ethics Review form and pass in your list of papers that require review. 
5. Now Ethics Chairs will be able to assign Ethics Reviewers to the flagged papers from their Ethics Chairs console. Ethics Reviewers will see the option to post Ethics Reviews to their assigned papers. 


---

# 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.openreview.net/how-to-guides/workflow/how-to-enable-an-ethics-review-stage.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.