Program Settings: open/closed defaults, judge conflicts, launch

Q: Program Settings: open/closed defaults, judge conflicts, launch

Program Settings Found at Admin → Program Settings . This is the control panel for whole-of-program defaults: most other pages (Categories, Judges, Users) can override these on a case-by-case basis, but this page shows you the defaults and any exceptions in one place. Entries / Payments / Judging: open or closed Each of the three has a program-wide default (open or closed). Individual categories can override the entries/judging default, and individual users can override the payments default: this page lists any category or user that's currently set differently from the default, so you can spot exceptions at a glance rather than checking every category or user one by one. Judge conflict-of-interest policy Controls what happens when a judge is also an entrant in the program, ordered from least to most restrictive: No conflict management : admins may assign judges freely. Allow, but exclude own scores : a judge can be assigned their own entry; it's flagged, and their score on it is dropped when final scores are calculated. No judging own entry : a judge can judge a category they entered, just not their own entry. No judging own category : a judge can't judge any category they have an entry in at all. Judges cannot enter , the two roles are kept fully separate: a judge can't be an entrant and an entrant can't be made a judge. Pick the level that matches how strict your program needs to be; this is enforced automatically everywhere judges are assigned or scores are calculated, no manual checking required. Ready to launch? The same page shows whether your program is ready to open to the public (payment/licence status, required setup steps). See howto-launch-portal for the full launch flow.

Question

Accepted Answer

Program Settings

Found at Admin → Program Settings. This is the control panel for whole-of-program defaults: most other pages (Categories, Judges, Users) can override these on a case-by-case basis, but this page shows you the defaults and any exceptions in one place.

Entries / Payments / Judging: open or closed

Each of the three has a program-wide default (open or closed). Individual categories can override the entries/judging default, and individual users can override the payments default: this page lists any category or user that's currently set differently from the default, so you can spot exceptions at a glance rather than checking every category or user one by one.

Judge conflict-of-interest policy

Controls what happens when a judge is also an entrant in the program, ordered from least to most restrictive:

No conflict management: admins may assign judges freely.
Allow, but exclude own scores: a judge can be assigned their own entry; it's flagged, and their score on it is dropped when final scores are calculated.
No judging own entry: a judge can judge a category they entered, just not their own entry.
No judging own category: a judge can't judge any category they have an entry in at all.
Judges cannot enter, the two roles are kept fully separate: a judge can't be an entrant and an entrant can't be made a judge.

Pick the level that matches how strict your program needs to be; this is enforced automatically everywhere judges are assigned or scores are calculated, no manual checking required.

Ready to launch?

The same page shows whether your program is ready to open to the public (payment/licence status, required setup steps). See howto-launch-portal for the full launch flow.