Review setup connects several records. A space has rounds and buckets, and each round names the team for a bucket. A round can also name a review form or decline reason, while your review settings name a starting round and a default bucket. Rhythm stops you from deleting a round, bucket, team, form, page layout, or integration function while another record still depends on it. Rhythm also stops you from deleting a space while it still has rounds or buckets.
Prerequisites
- To delete a review round or bucket, you need
submissions:user:review-rounds:*orsubmissions:user:review-buckets:*, respectively. Without the matching key, the Console keeps you off those setup pages instead of showing them in read-only mode.
What Blocks a Delete
| You are trying to delete | Blocked while |
|---|---|
| A review round | It is the starting round in your space's review settings, or a submitted review is recorded against it |
| A review bucket | Your review settings name it as the default bucket or use it in a bucket assignment rule, or any round still assigns it to a team |
| A review team | Any round still assigns that team to one of its buckets |
| A review form or the source-record page layout reviewers see | Your review settings, or any round's override, still names it |
| An integration function used to choose reviewers | Any round still uses that function for a bucket's reviewer assignment |
| A space | It still has any review rounds or buckets |
One support case showed this chain during cleanup. Review buckets and review teams could not be removed because they were still connected to open review rounds, and those rounds were tied to abstracts that had already been submitted. Deleting the submitted abstracts was not the fix; the review setup needed to be unwound in the right order.
A cloned event can leave you in the same position from a different starting point. Cloning copies a space's review buckets, teams, and rounds, along with the relationships behind them. Those copied relationships can make the review setup in the cloned event just as hard to clear out as a long-used one, even though the clone is new. Unwind the copied rounds, buckets, and teams in the same order described here rather than assuming a freshly cloned space has nothing attached to it yet.
Warning
Restricting a criterion on your review form to specific rounds or buckets does not protect those rounds or buckets from deletion. If you delete a restricted bucket or round, the criterion still points to a saved reference that no longer matches anything, and Rhythm does not clean it up automatically.
Deleting a Review Round
- Go to Spaces › Setup › Reviews › Rounds.
- If the round is your space's starting round, open Spaces › Setup › Reviews › Settings, choose a different starting round, and save.
- Return to the rounds list and select the round's delete icon.
- Confirm the dialog: Are you sure? / You are deleting [round name]. This operation cannot be undone. / Yes, delete it!
Result
The round is removed from the list. If a submitted review is still recorded against the round, Rhythm refuses the delete because you cannot delete a round that reviewers have already used.
Deleting a Review Bucket
- Go to Spaces › Setup › Reviews › Buckets.
- Open Spaces › Setup › Reviews › Settings. If the bucket is your default bucket or appears in a bucket assignment rule, choose or remove that reference and save.
- Open Spaces › Setup › Reviews › Rounds, edit any round whose bucket assignments still include this bucket, remove that assignment, and save the round.
- Return to the buckets list and delete the bucket, confirming the same Are you sure? dialog.
Result
The bucket is removed once nothing still names it. A criterion restricted to the bucket is not affected, and Rhythm does not warn you about it; see the warning above.
Deleting a Review Team, Form, Layout, or Integration Function
These records live on other setup screens, but review rounds and settings can still depend on them:
- A review team cannot be deleted while a round's bucket assignment still lists it. Edit the round first, then reassign the bucket to a different team or remove the strategy that names the team before you delete the team. Other related records, such as processes or reviews still referencing the team, can block the delete the same way; remove those relationships too before you try again.
- A review form or page layout used by your review settings, or overridden on a specific round, cannot be deleted while it is named there. Choose a different form or layout in Review Settings or on the round, then delete it.
- An integration function that a round uses to choose reviewers for a bucket cannot be deleted while that round still uses it. Change the bucket's reviewer-assignment strategy on the round first.
Deleting a Space
You cannot delete a space while it still has any review rounds or buckets. Delete every round and bucket first, in the order above, and then delete the space itself. See Edit, Close, and Delete a Space for the rest of what blocks a space delete, including submissions and submission types.
Permissions
Deleting review rounds and buckets requires the same keys you use to edit them (submissions:user:review-rounds:* and submissions:user:review-buckets:*). Deleting review teams, forms, layouts, and integration functions each falls under the setup permissions for that area.
Validation and Errors
When something still depends on the record, the Console refuses the delete and shows a failure toast with the server's message. There is no single error message that lists every dependent record at once. If more than one thing points to the record you are trying to delete, resolve them one at a time and retry the delete after each change.