Skip to Content
RhythmHelp Center
/

Available Documentation

  • Platform
  • CRM
  • Portals
  • Security & Settings
  • Accreditation
  • Membership
  • Finance & Billing
  • Orders & Inventory
  • Events
  • Certifications
  • Awards
  • Careers
  • Fundraising
  • Integrations
  • Sponsorships
  • Submissions

Coming Later

  • DocumentsComing Soon
Submissions
  • Overview

Subjects

  • Concepts
    • Overview
    • How Rhythm Decides What a Member Can Submit
    • Online Forms Pages in the Portal
    • Mirrored Submissions Explained
    • How Submissions Are Identified and Kept Consistent
    • Removing and Protecting Submissions
    • Spaces Explained: Kinds, Identifiers, and Status
    • Finding Your Way Around Spaces in the Console
    • How Review Setup Works
    • Review Teams and How Their Members Are Found
    • View All Articles
  • Tasks
  • Portal
  • Configure
  • Troubleshooting
  1. Home
  2. Submissions
  3. Concepts

Review Teams and How Their Members Are Found

review team ‧ reviewer team ‧ committee review team ‧ organization review team ‧ dynamic team membership ‧ who can review ‧ review team members

On This Page
  • Three Ways a Team's Members Are Found
  • Committee Membership Follows the Term, Not Just Current Membership
  • Organization and Committee Teams Stop at 100 Members
  • Which Rounds and Buckets a Person Can Reach
  • Related

A review team is the group of people Submissions uses as reviewers, or as review-team administrators, for one space. Each review team belongs to one space, so it is not shared across spaces like a submission process or custom field.

Three Ways a Team's Members Are Found ​

When you set up a review team, you choose how Rhythm finds its members:

  • A hand-picked list. You add each person directly.
  • An organization's contacts. The team includes people who hold the matching role for the organization you choose, such as everyone with a "Reviewer" role on a committee's parent organization.
  • A committee's current members. The team includes the people who currently belong to the committee you choose.

The organization and committee options are dynamic. Instead of saving a fixed list, Rhythm checks who belongs on the team each time it needs that information. When someone joins or leaves the organization or committee the team follows, the review team updates automatically, so you do not have to edit it by hand.

Tip

You can find setup steps for dynamic teams and review teams in the related configuration articles.

Committee Membership Follows the Term, Not Just Current Membership ​

For a committee-based team, Rhythm checks whether the person belongs to the committee and whether their committee term is current. When the term and the person's committee membership both have dates, Rhythm uses the term dates, even if the membership dates are more specific. This means someone can still appear as a committee member in your records but be left out of the review team after their term ends.

Organization and Committee Teams Stop at 100 Members ​

A review team built from an organization or committee can include up to 100 people. If an organization has more than 100 contacts with the matching role, or a committee has more than 100 members, only the first 100 count for review assignment. This limit is fixed, so you cannot raise it for a specific account or team.

A hand-picked team does not have this built-in limit because you choose each member yourself.

Which Rounds and Buckets a Person Can Reach ​

Being on a review team does not, by itself, decide which parts of a space someone can review or administer. That access depends on which rounds have bucket assignments for the person's teams. Rhythm checks every team the person belongs to that has been assigned to a round and, through that assignment, to a bucket. If the same access comes from more than one team, such as two teams that reach the same round and bucket, Rhythm does not remove the duplicate; it simply confirms that the person has access.

This check does not consider whether a round is open, closed, or within its dates. It only checks whether one of the person's teams has been assigned there. If your space has several dynamic teams, Rhythm checks each team's current membership every time it answers this access question instead of using a saved answer, so changes to committee membership or organization roles take effect right away.

Related ​

Review teams work alongside reviewer assignments, which connect one reviewer to one submission. A person can be on a team before any submissions are assigned to them.

Continue in This Subject

PreviousHow Submission Counts WorkNext Reviewer Assignments and Their Status

Related Articles

  • Set Up a Review Team

    How to create, change, reorder, and delete a space's review teams, choose a hand-picked team's members and their roles, and build a team automatically from an organization or a committee.

  • Build a Review Team from an Organization or a Committee

    Make a review team follow an organization's contacts or a committee's current members automatically, and map contact roles or committee positions to reviewer roles, instead of typing a fixed member list.

  • Reviewer Assignments and Their Status

    A reviewer assignment links one reviewer to one submission and moves between not-yet-reviewed, reviewed, and declined as reviews are saved, changed, or deleted -- and it's part of why some records can't be deleted while assignments still name them.

  • A Record's RelationshipsCRM

    What staff see on a contact's or organization's Relationships tab, what current, past, and future mean there, and why relationships are a Console feature with no equivalent for members on the Portal.

On This Page

  • Three Ways a Team's Members Are Found
  • Committee Membership Follows the Term, Not Just Current Membership
  • Organization and Committee Teams Stop at 100 Members
  • Which Rounds and Buckets a Person Can Reach
  • Related
Rhythm Help Center© Rhythm Software

Search article titles, settings, tasks, and troubleshooting topics. Press Enter to see results.

Browse Platform Documentation