> 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/getting-started/hosting-a-venue-on-openreview/customizing-your-submission-form.md). # Customizing your submission form For an overview and basics of form customization, see the comprehensive [Customizing Forms](/getting-started/customizing-forms.md). ### For Conference Review Workflow Venues: To make changes to your submission form, navigate to your Workflow Timeline. Then go to the "Submission" Step — > Edit Fields — > Widget. This will allow you to edit the fields in your submission form. {% hint style="info" %} To hide a new field from reviewers, go to "Submission Change Before Bidding" and/or "Submission Change Before Reviewing" — > Edit Hide Fields. You can check which fields are visible to reviewers by going to any submission page and hovering over the eye icon next to the field name. {% endhint %} ### For Request Form Venues: You can customize the [default submission form](/reference/default-forms/default-submission-form.md) for your venue using the [Revision](/reference/stages/revision.md) button on your [venue request form](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#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. Shown below is an example of adding a field for authors to nominate a reviewer from the author list of their paper. {% tabs %} {% tab title="Website" %}
{% 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:
## Common Customizations ### Asking authors to agree to conference policies 
{
  "confirmation": {
    "description": "Please confirm you have read the workshop's policies.",
    "order": 2,
    "value": {
      "param": {
        "type": "string",
        "enum": [
          "I have read and agree with the workshop's policy on behalf of myself and my co-authors."
        ],
        "input": "radio"
      }
    }
  }
}
### Limit read-permissions for certain fields The `readers` field can be used to list who will be allowed to read a specific field of the submission form. The example below limits the readers of the `private comments` field to just authors, Assigned Senior Area Chairs, and Program Chairs. Note: Authors will not be able to read these fields if they are not in the readers list
```json { "private_comments": { "value": { "param": { "type": "string", "optional": true } }, "readers": [ "Your/Venue/ID/Program_Chairs", "Your/Venue/ID/Submission${4/number}/Senior_Area_Chairs", "Your/Venue/ID/Submission${4/number}/Authors" ] } } ``` ### Adding tracks to your venue Once you have [reviewed our support for "tracks" in a single venue](/how-to-guides/workflow/how-to-have-different-tracks-or-types-of-submissions-for-a-single-venue.md) and you think this is what your venue needs, you can add a "track" field to your submission form if you are using separate reviewing pools for track submissions.
```json { "track": { "description": "Please select the track you are submitting to.", "order": 2, "value": { "param": { "type": "string", "enum": [ "Track 1", "Track 2", "Track 3" ], "input": "radio" } } } } ``` --- # 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/getting-started/hosting-a-venue-on-openreview/customizing-your-submission-form.md?ask=&goal= ``` `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.