Restrict access to tasks for performers who fail to enter captcha several times in a row. This helps protect you from robots.

To show a captcha to performers, set captcha frequency in the pool settings.


The If and then fields in this rule are mandatory. If you don't fill in at least one field, you won't be able to save the rule.

Rule settings



Recent values to use

The number of times the performer was shown a captcha recently.

To calculate all captcha displays in all pool tasks, fill in the field in the rule for each project pool.

If this field is not filled in, only the captcha displays when completing tasks in the pool that uses this rule are counted in the calculation.


A condition for performing the action in the then field:
  • number of responses — The number of entered captchas (less than or equal to the number in the Recent values to use field).

  • correct responses (%) — The percentage of correct responses (from 0 to 100).

  • % incorrect answers — The percentage of incorrect responses (from 0 to 100).

To add multiple conditions, click .


Action to perform for the condition:

  • assign skill from the field — Save the percentage of the performer's correctly entered captchas in tasks as a skill value.

  • Ban — Block access to the project or all requester's projects for the specified number of days. Only the requester can view the reason for the ban.

    If access to tasks is blocked temporarily (for example, for 7 days), the history of the performer's responses is not saved after the ban is lifted. The skill value is based on new responses.

  • Suspend — Suspend the performer's access to the pool for the specified number of days. Only the requester can view the reason for the ban.

  • accept user's answers — Requires the non-automatic acceptance option to be set.

    Useful if the performer completes most tasks well. Example: the toloker completed more than 80% of the tasks correctly and you are satisfied with this result. The rule will work automatically — all responses in the pool will be accepted.

  • decline user's answers — Requires the non-automatic acceptance option to be set.

    Useful if you need several responses from the performer to evaluate the quality of the results. Example: after ten responses, it became clear that the performer completes tasks poorly. The configured action will work — all responses in the pool will be rejected.

  • Assign skill value — Assign a fixed value to the skill.

Rule example

Blocking for incorrect captcha entries

If the performer entered a captcha at least 5 times and the percentage of correct answers is less than 65%, they are banned and can't complete your tasks for 10 days.


Should I create a skill for every pool?

It is better to use one skill in a project. You can choose the way to calculate the skill:

  • Calculate the skill for each pool separately. The current skill value is the value of the skill in the pool the user completed last. This option is convenient if:

    • The pools are intended for different groups of performers (for example, there are filters by city or country).

    • Pools are started one by one and you don't want to take into account the responses in the previous pools to calculate the skill in the current pool.

    This calculation method is used by default when adding a quality control rule to a pool. For the control tasks block, leave the Recent values to use field empty.

  • Calculate skill based on all tasks in a project This option is good if the pools are small and you don't need to have skill calculated for each pool.

    This option is available only for skills on control tasks. To use it, fill in the Recent values to use field in quality control rules in pools.

Can I use a skill beyond a particular pool or project and apply it to other projects as well?

Yes, of course — you can use the same skill for different projects. But most often, a skill is intended for a specific project. If the performer completes a certain task well, this doesn't mean that they will complete other ones successfully. Another disadvantage is that if you filter by skills that were set long ago, you will artificially limit the number of available performers.