> 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/v1/getting-started/hosting-a-venue-on-openreview/customizing-your-submission-form/allowing-authors-to-nominate-an-author-as-reviewer.md).

# Allowing authors to nominate an author as reviewer

You can add a field for authors to nominate co-authors as reviewers by editing the submission form.

You can customize the [default submission form](https://docs.openreview.net/reference/default-forms/default-submission-form) for your venue using the [Revision](https://docs.openreview.net/reference/stages/revision) button on your [venue request form](https://docs.openreview.net/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages#venue-request-form). In the 'Additional Submission Options', field, enter valid JSON with the fields that you would like to add or change in your form.

{% tabs %}
{% tab title="Website" %}

<figure><img src="https://622636955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVorH499wd7ipUjYX5etp%2Fuploads%2FSs6O1RURJXxqZ7Zxn70l%2Fimage.png?alt=media&#x26;token=8951f0a9-26f2-4344-819a-bf1ddc396c74" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="JSON" %}

```json
{
   "serve_as_reviewer": {
      "value": {
          "param": {
            "type": "profile[]",
            "regex": "~.*"
          }
      },
      "description": "Please nominate an author to serve as a reviewer using their profile ID (e.g. ~First_Last1)",
      "order": 20
   }
}
```

{% endtab %}
{% endtabs %}

The resulting field in the submission form would look like this:

<figure><img src="https://622636955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVorH499wd7ipUjYX5etp%2Fuploads%2FREiFU2oCr0s29Ol02pVY%2Fimage.png?alt=media&#x26;token=bc022b39-7021-4821-89bc-cb4ec8510316" alt=""><figcaption></figcaption></figure>

The above field allows authors of submissions to nominate one or more co-authors to serve as reviewer. In order to check that the co-authors being added to this field are indeed an author of the submission, you need to add the following preprocess function to the submission invitation.

```
async function process(client, edit, invitation) {
    client.throwErrors = true
    
    const { note } = edit

    if (note.ddate) {
      return
    }

    const profiles = await client.tools.getProfiles(note.content.authorids.value)
    const profileIds = profiles.map(profile => profile.id)

    let reviewerAuthorField = note.content.serve_as_reviewer?.value
    if (reviewerAuthorField) {
      const reviewerAuthorFields = Array.isArray(reviewerAuthorField) ? reviewerAuthorField : [reviewerAuthorField]
      const reviewerAuthorProfiles = await client.tools.getProfiles(reviewerAuthorFields.map(field => field.includes('@') ? field.toLowerCase() : field))
      const invalidReviewerAuthor = reviewerAuthorProfiles.find(elem => !profileIds.includes(elem.id));
      if (invalidReviewerAuthor) {
        return Promise.reject(new OpenReviewError({ name: 'Error', message: 'Enter a paper co-author to serve as a reviewer. ' + invalidReviewerAuthor.id + ' does not appear in the author list' }))
      }
    }
}
```

To add this preprocess code, navigate to your venue's submission invitation: <https://openreview.net/invitation/edit?id={venue\\_id}/-/Submission>, scroll down to the process functions and click on the "Pre Process" tab.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openreview.net/v1/getting-started/hosting-a-venue-on-openreview/customizing-your-submission-form/allowing-authors-to-nominate-an-author-as-reviewer.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 `build a script that syncs our docs to a CMS` 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.