Результати пошуку
Settings → Permissions is the list of people who may administer your space and what each of them is allowed to do. Access is built out of three things:
Every permission you can tick on a principal or a policy, and what holding it lets someone do. The permission form groups them by area and labels them Read, Write, Configure, Delete, Testing, Admit and Assign; the tables below follow the same grouping.
This page is the set of answers to "what do I tick to make this person a judge?" — a worked list of the common jobs and the permissions each one needs. The model behind them is in Access management, and every individual permission is listed in Permission reference.
On-site printing lets contestants at a physical venue send a document to a printer in the room without having any network access of their own. You register the printers here, in Settings → Printers; a printer client running at the venue connects to Eolymp using the printer's secret, reports whether it is free, and receives jobs one at a time.
The Programming languages setting on Settings → General → Runtime is the list of languages and compilers members can choose from when they solve a problem. By default every language the platform supports is offered; restricting the list narrows what appears in the language picker on the public site.
Visibility decides whether someone who isn't signed in can see anything on your space's website. It is a single setting on Settings → General, on the General card, with two values:
A space is your own corner of the platform. It has its own website, its own members, and its own problems, contests, courses and content — none of it shared with any other space. People usually organise a space around a thing that persists: a school, a training club, a national olympiad, a university course, a company's hiring process.
Submissions is every solution submitted anywhere in your space — from a problem page, from the practice site, from inside a contest — in one list, newest first. It's where you find a particular attempt, watch testing as it happens, and read why a program failed.
Rejudging re-runs the evaluation of a submission that has already been judged, and replaces its result with the new one. You do it after changing something the old result was based on — a test that was wrong, a checker that was too strict, a limit that was too tight — and after a System failure, which usually means the problem's testing configuration was broken rather than the program.
Every submission carries two separate fields, and they are routinely confused. The status says how far the evaluation got. The verdict says how the program did, and only exists for an evaluation that ran to completion.