Auth types: basic, intermediate, unlimited, admin.
The auth type of a project is the max auth type of all project admins.
- basic user, basic project: as expected.
- basic user, unlimited project: GIS features still count towards limit.
- unlimited user, basic project: no limits.
- unlimited user, unlimited project: no limits.
This is a simple case as the limit is entirely attached to the user.
- basic user, basic project: back of queue.
- basic user, unlimited project: back of queue.
- unlimited user, basic project: front of queue.
- unlimited user, unlimited project: front of queue.
This is also a simple case as the limit is based entirely on the user auth level.
The :priority-queue-weight config value determines queue position. Lower numbers are given precedence over higher numbers. Nil is treated as zero.
Maximum jobs per week is defined by 2 limits: per-user and per-project. Users cannot exceed either.
- basic user, basic project: limit jobs per week on that project. Jobs run also count towards the per-user job limit.
- basic user, unlimited project: basic users will not be able to run more than their per-user limit, even on unlimited projects. Other basic users could still run jobs on this unlimited project, though.
- unlimited user, basic project: The unlimited user will not be able to run more than the per-project limit.
- unlimited user, unlimited project: no limits.
- basic user, basic project: job runtime limited
- basic user, unlimited project: no runtime limit on jobs.
- unlimited user, basic project: job runtime limited.
- unlimited user, unlimited project: no limits.
The restriction is based entirely on the project auth level. This makes sense given that it’s a setting on a project.