Two different settings are called “review team access.” One controls which team members can manage reviewers in the Portal. The other controls who can see which teams a person belongs to. This article explains both.
Prerequisites
- To open a review team’s or reviewer’s 360 page in the Console, you need view access to the space’s review teams (
submissions:user:review-teams:viewor broader). - A review-team administrator can manage reviewers in the Portal only when that option is turned on in the space’s review settings, as described below.
Where to Find It
Staff open Review Team 360 by selecting a team’s name from another review screen, such as the review 360, a round’s Buckets tab, or a bucket’s Teams tab. There is no direct menu item for this page. A reviewer’s own 360 page is at Spaces › [space name] › Reviews › [reviewer name].
Seeing Who’s on a Team
Review Team 360 shows:
| Tab | Content |
|---|---|
| Members | Every team member and their role: reviewer, administrator, or administrator/reviewer |
| Buckets | The round and bucket combinations this team reviews |
| Reviews | Reviews submitted by this team’s members |
| Outstanding / Declined | Assignments this team’s members have not completed yet, and assignments they have declined |
Tip
For a team whose members are chosen by hand, the Members tab shows the people you added directly. For a team built from an organization or committee, Rhythm works out membership dynamically instead of storing it on the team record, so this tab may not always show the latest membership.
Finding a Person’s Team Memberships
To see every review team a specific person belongs to, staff have two options:
- In one space: open that person’s Reviewer 360 page within the space to see their team memberships, role, and progress there.
- Across every space: open the person’s Contact record and review their review-team memberships, which lists every panel they sit on across your whole account.
To check whether a person belonged to a specific team in the past, and when that membership changed, look at the account’s audit log. This can help explain an assignment error that referenced team membership: the log can show that the person was not yet on the team when the error occurred, and exactly when someone later added them.
What Portal Members Can See
Anyone signed in to your Rhythm account’s Portal can open a review team and see its full roster, including each member’s role. This is also true for a round that uses blind review, because blind review does not hide review-team membership. In the Portal, a member can look up only their own team memberships; the Portal does not return another person’s team memberships.
If the space or round includes review instructions, Rhythm shows them in the Portal to every member of a review team, not just administrators. Use those instructions to tell reviewers what you expect during the review process and who to contact if they need help.
Controlling Whether Team Administrators Manage Reviewers in the Portal
A review-team administrator, or chair, can assign, edit, and remove reviewers from the Portal only when that team administrator permission is turned on in the space’s review settings. When it is turned off, reviewers can be managed only from the Console. See Review Settings for a Space for the complete list of rights and how to turn each one on or off; the “Assign, edit, and remove reviewers” checkbox there controls this permission.
This permission can also be overridden for a specific round. If team administrators can manage reviewers in some rounds but not others, check the round’s own settings instead of assuming the space’s review settings apply everywhere.
Permissions
Opening a review team’s or reviewer’s 360 page requires view access to review teams in that space. Changing whether team administrators may manage reviewers in the Portal requires the same permission used for review settings generally (submissions:user:review-settings:configure).
Validation and Errors
If you do not have the needed view permission, the Console shows the standard access-denied prompt instead of opening the team’s or reviewer’s 360 page. It does not show a blank or partial page. There is no separate error state specific to these pages, except when a team or reviewer identifier does not resolve, which the Console does not describe with a specific message.