The jury role is sufficient (and often personalized) for problem import. So I would not do this but encourage users to create a jury account before doing so.

We could check whether there's a team associated in the import script and ask for confirmation to proceed if not?

The jury role is sufficient (and often personalized) for problem import. So I would not do this but encourage users to create a jury account before doing so.

Sounds reasonable

We could check whether there's a team associated in the import script and ask for confirmation to proceed if not?

That should be doable and is a better option.

Reopening as the intent doesn't match the code.

Currently a jury member can't upload problems via the GUI (and neither via API see:

@meisterT what should be changed? My original question or should we let jury members allow to upload problems? For the last part I would say using API_Writer is the better choice and maybe create a custom role for bapctools so a jury member can't break config easily and only via certain tools?