Concepts

Why one member sees a submission form that another does not, and how a space's owner type, submission window, eligibility, role restriction, and submission limit combine to decide it.

The Online Forms pages Submissions adds to the Portal, where they sit in the Portal menu, how a member moves between them, and why they show your space's own words for a submission.

How Rhythm automatically copies event abstracts, award applications, membership applications, certification applications, and accreditation reports into review spaces, and what happens to a mirror as its source record changes.

What a submission's identifier is, why it always starts with its space, and why Rhythm refuses to save a submission whose origin, type, process, bucket, or round does not belong to that space.

When Rhythm removes a mirrored submission for you, when it keeps one instead, and why you cannot delete a contact, organization, space, or setting that submissions still depend on.

A space is the one container that holds everything you set up and run for a collection in Submissions, from a conference's abstracts to a free-standing Portal form, with a kind, an identifier, and a status that decide how it behaves.

Where the Submissions Console lists your spaces, how a space's own menu and setup pages are laid out, and what to expect from the account-wide setup overview and a link to a space that no longer exists.

How a space's review settings, rounds, buckets, and teams fit together, what order to set them up in, and whether a round is still open once its deadline has passed.

How Rhythm sorts a new submission into a bucket using the space's ordered rules, and how the round's strategy then decides who reviews it — the whole team, the least-loaded members in turn, people staff choose, or your own custom logic.

How a review's total score and recommendation are worked out, how Rhythm combines every review in a round into the totals and overall recommendation shown on a submission, and which round supplies the headline figures.

What the four Submissions counts are, why a count can lag behind what you just changed, and why letter case never affects a count's answer.

A review team belongs to one space and finds its members one of three ways -- a hand-picked list, an organization's contacts, or a committee's current members -- which decides who Rhythm treats as able to review or administer that space's rounds and buckets.

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.

Rhythm emails a submission's expected reviewers when it lands in or moves to their bucket and round, using the round's notification settings if it has any and the space's otherwise, and one failed email never stops the rest from going out.

When a mirrored submission's status, scores, or placement change, Rhythm writes the outcome back onto the record it came from, so staff working in that record's own application can see review progress without opening Submissions.