For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to Hide and Unhide Submission Fields from Reviewers

Two steps in your venue's Workflow Timeline decide which submission fields reviewers can see:

  • Submission Change Before Bidding runs 30 minutes after the submission deadline. It gives all Reviewers access to the submissions so they can bid. By default it hides the author identities and the PDF.

  • Submission Change Before Reviewing gives assigned Reviewers access to the submissions they review. By default it hides the author identities, and the PDF becomes visible again.

A hidden field is visible only to the readers you list for it. By default, these are the venue group, which includes the Program Chairs, and the submission's authors.

  1. Go to the Workflow Timeline and find the Submission Change Before Reviewing step. The Workflow Timeline lists it as Create Submission Change Before Reviewing.

  2. Click Edit next to Restrict Field Visibility. The Content Readers editor shows the current settings as JSON. The authors entry is already there.

  3. Add an entry for each field you want to hide, using the field name from your submission form. Copy the readers list from the authors entry. For example, to hide a field named financial_aid:

    {
      "authors": {
        "readers": ["<venue_id>", "<venue_id>/Submission${{4/id}/number}/Authors"]
      },
      "financial_aid": {
        "readers": ["<venue_id>", "<venue_id>/Submission${{4/id}/number}/Authors"]
      }
    }

    Keep the other entries that are already in the editor, and set the pdf entry to "pdf": { "readers": { "const": { "delete": true } } } so assigned reviewers can see the PDF. To keep the PDF hidden from them instead, give the pdf entry the same readers list.

  4. Click Submit.

  5. To hide the field while Reviewers bid as well, repeat steps 2 to 4 in the Submission Change Before Bidding step.

The Create Submission Change Before Reviewing step expanded in the Workflow Timeline, with the Restrict Field Visibility editor open showing the default Content Readers JSON.
The default Restrict Field Visibility settings of Create Submission Change Before Reviewing, as Program Chairs see them.

Each step applies its settings on its Activation Date. After that date has passed, the step runs again each time you edit it, so your changes reach existing submissions right away. When you deploy assignments, the Activation Date of Submission Change Before Reviewing moves to 30 minutes after the deployment. To run the step now, click Edit next to Dates and set the Activation Date to the current time.

Make a hidden field visible again

To make a field visible to everyone who can read the submission again, set its readers to { "const": { "delete": true } } in the Content Readers editor. For example, to show the PDF:

Keep the other entries, click Submit, and the step removes the field's restriction from existing submissions the next time it runs.

Last updated

Was this helpful?