Quotas and limits

A quota is a limit your plan places on the space: how many contests it may hold, how many submissions may be evaluated in a month, whether a feature exists at all. Quota is a property of the plan, so changing plan changes every limit at once; a custom subscription arranged with us carries its own quota attached to the space instead.

The quota your space has right now is listed on the subscription card at Settings → Billing, and each plan card in the plan chooser lists what that plan would give you. This page is the full set.

How to read a quota

Quotas come in two shapes, and they fail differently.

A switch is a feature the plan either includes or does not. Team competitions, plagiarism analysis, single sign-on and discussions work this way. When the switch is off the feature is absent: the setting, tab or option is not shown to anyone in the space, including the owner, and no permission brings it back.

A number is a cap on how many of something you may have or use. Problems, contests, seats' worth of evaluations, automation rules. The feature exists, and it stops working when you reach the cap.

The two overlap at zero. A numeric quota set to zero behaves exactly like a switch that is off — zero printers hides the Printers tab, zero achievements removes achievements, zero automation rules removes the Automation section. So "my plan doesn't have it" and "my quota is zero" describe the same thing from the outside, and both are fixed the same way: by moving to a plan that includes it.

What that means when you are looking for a missing button: if a colleague who administers the same space cannot see it either, it is the plan. If they can, it is your permissions. Why a section is missing works through this.

General

Quota	What it limits
Administrator accounts	How many people may hold permissions in the space.
Single sign-on	Whether Google Workspace and OpenID Connect sign-in may be configured.
Dedicated user database	Whether the space may keep its own member accounts instead of using Eolymp accounts.
Custom profile fields	How many custom attributes members may have.
Customer support reply time	The response time we target for your support requests, in hours.
Discussions	Whether posts and comments exist at all.
Achievements	How many achievements the space may define; zero removes the feature.
Printers	How many printers may be registered; zero hides the Printers tab.

Submission evaluation

Quota	What it limits
Monthly evaluations per seat	Multiplied by your seat count to give the space's evaluation budget for the month. Rejudges count against it.
Priority evaluation queue	Whether submissions are tested on the priority queue.
Plagiarism analysis	Whether similarity reports over submitted code are available.
Submission evaluation limit	The longest wall-clock time a single submission may spend being evaluated.

Members

Quota	What it limits
Members in total	How many members the space may hold.
Member credits	Whether members can hold credits.

Members in total is a separate limit from seats: seats are how many members may sign in during a billing month, the member quota is how many member records the space may contain. See How billing works.

Newsletters

Quota	What it limits
Campaigns per space	How many newsletters the space may have; zero removes the feature.
Emails per day	How many emails may be sent in a day.
Emails per month	How many emails may be sent in a billing month.

Automation

Quota	What it limits
Automation rules	How many rules the space may have; zero removes the Automation section.
Automation executions per month	How many times rules may run in the current billing period.

AI

Quota	What it limits
AI tokens per month	Prompt and completion tokens available per billing period; zero disables AI features.

Scoreboards and courses

Quota	What it limits
Scoreboards per space	How many scoreboards the space may have.
Courses per space	How many courses the space may have.

Problems

Quota	What it limits
Problems in total	How many problems the space may hold.
Tests per problem	How many tests one problem may have.
Testsets per problem	How many testsets one problem may have.
Statements per problem	How many statement translations one problem may have.
Editorials per problem	How many editorial translations one problem may have.
Solutions per problem	How many reference solutions one problem may have.
Code templates per problem	How many starter templates one problem may have.
Debug assistant	Whether AI debugging help is available.
Debug hints per day (administrator)	An administrator's daily hint budget.
Debug hints per day (member)	A member's daily hint budget.

Contests

Quota	What it limits
Contests in total	How many contests the space may hold.
Active contests	How many contests may run at once, counting those open for upsolving.
Contests per month	How many contests may be started in the current billing period.
Problems per contest	How many problems one contest may contain.
Upsolve mode	Whether contests may stay open for upsolving after they end.
Maximum contest duration	The longest contest you may run.
Team competitions	Whether team contests may be created.
Ghost participants	Whether imported, non-interactive participants are allowed.
Unofficial participants	Whether participants outside the official standings are allowed.

Features that appear only when the quota allows

Feature	Turned on by
Printers	Printers quota above zero
Newsletters	Campaigns quota above zero
Achievements	Achievements quota above zero
Member credits	The member credits switch
Template generator	The template generator switch
Automation	Automation rules quota above zero
Discussions	The discussions switch

When a quota runs out

The action is refused at the moment you attempt it, and the console shows the error. Nothing is silently truncated, and nothing you already created is removed or hidden — a space that has hit its problem limit keeps all its problems and simply will not accept another.

The counters that most often bite:

Monthly evaluations. Submissions stop being evaluated for the rest of the quota period. Participants can still submit; their work is not tested. Rejudging consumes the same budget, so a full rejudge late in the month can exhaust it.
Active contests, contests per month. Creating, starting or reopening a contest is refused.
Problems, courses, scoreboards, printers, automation rules. Creating another is refused; the ones you have keep working.
Automation executions. Rules stop firing until the period rolls over.
AI tokens. AI-backed features stop responding until the period rolls over.
Emails per day, emails per month. Sends are refused.

Two things follow from the way periods work:

Monthly counters reset on the anniversary of the day you subscribed, not on the 1st.
Raising the seat count raises everything expressed per seat — evaluations, most visibly — immediately. See Change your plan or seats.