Every space has one review settings record. Use it to choose where new submissions start, which form reviewers complete, which original record fields reviewers see, what team administrators can do in the Portal, and whether reviewers receive automatic emails.
Prerequisites
- At least one review round and one review bucket must already exist in the space. The two required selects on this page stay empty until both exist.
- A review form must already exist, and its identifier must begin with the reviews prefix your account uses for review forms.
- You hold
submissions:user:review-settings:configure(or the Submissions Administrator policy).
Where to Find It
Go to Spaces › Setup › Reviews › Settings. A new space's Setup overview page also includes a short checklist that puts the review setup steps in a sensible order: configure a bucket, set up your review teams, configure a round, finalize your review settings, reprocess placement from Review Maintenance, and install the Reviews feature in the Portal. The last step links directly to the Portal's feature creation area, so you do not have to find it yourself. The checklist is only a fixed guide; it does not confirm whether you completed each step.
When abstracts will be reviewed for a specific event, review setup is split between two places. First, build the review form in the global Abstract › Review Forms setup area, because that is where review forms are created. Then finish the rest of the review settings from the event's own Abstracts tab, including the starting round, default bucket, and the other settings on this page. Opening abstracts on the event is what creates this space in the first place.
Tip
Installing the Reviews feature in the Portal is separate from adding an abstract-related page to your microsite. Downloading the abstracts feature also downloads an Abstract Review page, and it is easy to add that page without realizing reviewers still need the Reviews feature itself installed before assigned reviews appear for them. If the review center looks empty after you add pages, check that the Reviews feature is installed, not just an overview-style page.
The Settings
| Setting | Options | Default | Effect |
|---|---|---|---|
| Starting Round: | One of the space's rounds | None (required) | The round every new submission enters |
| Default Bucket: | One of the space's buckets | None (required) | Where a new submission goes when no placement rule matches it |
| Review Form: | One of your account's review forms | None (required) | The form reviewers complete for any round that does not override it |
| Page Layout for Reviewers: | One of your source application's page layouts, or blank | Blank (reviewers see every field) | The fields from the submission's original record that reviewers see |
| Reviewer recommendation prompt | On/Off, then prompt and guidance text | Off | Asks reviewers for an overall recommendation in addition to scores |
| Bucket Assignment Rules | On/Off, then an ordered list of rules | Off | Places new submissions in a bucket automatically based on the conditions you set |
| Instructions to Reviewers / Decline Instructions / Instructions to Administrators | Rich text | Empty | Guidance shown to reviewers, reviewers who decline, and team administrators in the Portal |
| Team Administrator Permissions (four checkboxes) | On/Off each | Off | What team administrators may do for this space's submissions in the Portal: move between rounds, move between buckets, mark a review status, and assign, edit, or remove reviewers |
| Reviewer Notification Emails | On/Off, then an email template | Off | Whether reviewers receive an automatic email when a submission is assigned to them |
Bucket assignment rules and scoring criteria have their own setup, covered in separate articles. You edit both from dialogs that open on this page.
The review forms you build here are specific to the Submissions & Reviews application. If another Rhythm application runs its own review process, such as an event's call-for-proposal abstract review, that process uses its own review form configured in that application's setup, not a form from this list.
Tip
Fields on the abstract review form appear to reviewers in a fixed two-column layout. There is no setting to switch this to a single column. Making the browser window narrower is the only thing that changes how the fields wrap, because the columns reflow responsively.
Team Administrator Permissions
The four team administrator permission checkboxes control whether review-team administrators, such as chairs, can manage submissions from the Portal. They can move submissions between rounds, move them between buckets, mark a submission's review status, and assign, edit, or remove reviewers. For a space that is not a Portal-form space, the mark-status checkbox changes the review status, not the submission's own status field, because those statuses are tracked separately. See Control Review Team Access in the Portal and Console for more on what a team administrator can do when these rights are turned on.
Reviewer Notification Emails
Turn on Automatically notify reviewers when a submission is assigned to them to send the email you write whenever a submission is placed into, or moved into, a bucket the reviewer covers. This is useful when new assignments happen sporadically over time instead of all at once, because reviewers do not have to keep checking back for new work. Each reviewer's contact record must have an email address to receive the email. A reviewer with no email address receives nothing, and Rhythm does not show a separate warning.
Warning
Selecting Preview next to the notification email does not currently show the message with your merge fields filled in. Do not rely on it to check your wording. Instead, submit a test submission through a sandbox and confirm the email a real reviewer receives.
Dependencies and Precedence
- The starting round and default bucket must belong to this space. If you choose one from another space, Rhythm refuses the change when you save.
- Bucket assignment rules can target only buckets that belong to this space.
- The review form you choose must be a review form that matches your account's reviews-form naming, not another kind of web form.
- The Review Form setting controls which form reviewers complete, but the Portal can also be affected by how the submission itself was collected. When the review form in the Portal did not match what was configured, the cause was a mismatch between the submission process's own form and the reviewer form. For example, the submission process used a different abstract-form layout than the review form expected. If your reviewers see something unexpected, compare the submission form's layout to the review form before assuming the review settings are wrong.
Warning
Saving review settings never changes records that already exist. A new scoring criterion does not alter reviews already submitted, and a new bucket assignment rule does not move submissions already placed. To apply a new rule or a new default bucket to existing submissions, run Reprocess Bucket Assignments from Review Maintenance afterward.
Permissions
One permission controls all review settings: submissions:user:review-settings:configure. The Submissions day-to-day user and Submissions Administrator policies include it. You cannot grant access to only part of this page; a staff member who can open it can change everything on it.
Validation and Errors
Starting Round, Default Bucket, and Review Form are required. You cannot save review settings until you choose all three, and you cannot choose them until the space has at least one round and one bucket. If you choose a round or bucket from a different space, Rhythm refuses the change and shows a message naming the record and the space it belongs to. If a save fails for any other reason, the Save Changes button can stay in its saving state. If that happens, reload the page and redo your changes instead of waiting for it to recover. If your space has no scoring criteria configured yet, try adding at least one review criterion before saving again, because that has cleared up a stuck save in some cases.