Publish a problem

Publishing puts a problem in your space's public catalog, where participants can find it and solve it. Until then it exists only in the console: problems you create and problems you import both start unpublished.

You need permission to write problems.

Publish

Open Problems.
Either open the problem and use Publish in its header, or use Publish from the row's menu in the list.
Confirm.

There are no options in the dialog. The Visible column changes to Published, and the problem appears at /problems/<number> on your space's public site — the number is the one shown in the problems list. The row's View action, which is offered only for published problems, opens exactly that page.

Before you publish

Nothing here is enforced, and a problem with none of it will publish happily and grade nothing:

A statement in the languages your participants read, with the input and output formats and at least one example.
Tests, in testsets whose scoring and feedback are what you intend.
A checker, or an interactor, or both. Without one of them nothing can be graded.
Limits set in Testing → Configuration, and confirmed by running the reference solutions — the intended solution accepted, the naive one timing out.

Unpublish

Unpublish, from the same menu and with the same confirmation, takes the problem out of the catalog. Everything else survives: statements, tests, solutions, issues, history. Publish it again and it comes back as it was.

This is the reversible way to take a problem out of circulation — because you found a mistake, because you want to reuse it in a contest first, or because it was published early.

Delete

Delete removes the problem and everything in it — statements, tests, solutions, issues — permanently. There is no restore, and the confirmation is the only thing standing between you and that.

If what you want is for participants to stop seeing the problem, unpublish it instead.

What participants get

A published problem is readable, submittable and discussable by anyone who can see the catalog. The rest of the problem — test data, checker, interactor, reference solutions — is never exposed; see What participants see while solving.

Reports of mistakes come back to you through the problem's Issues tab.