Submitted responses

To involve as many Tolokers as possible, limit the number of tasks in the pool per Toloker or set a limit on daily earnings in your project.

When to use

Use this rule if you want to:

Get responses from as many Tolokers as possible. For this purpose, set a low threshold, such as one task suite.
Protect yourself from robots. For this purpose, the threshold should be higher, such as 10% of the pool's tasks.

Tip

Don't set large values in pools where Tolokers won't have time to complete the required number of tasks.

How to configure

Warning

All fields in this rule are required. If you don't fill in at least one of them, you won't be able to save the rule.

Field	Overview
If	A condition for performing the action in the then field: submitted task suites — The number of task suites in the pool completed by the Toloker.
then	Action to perform for the If condition: suspend — Suspend the Toloker's access to the pool for the specified number of days. Only the requester can view the reason. assign skill value — Assign a fixed value to the skill. ban — Block access to the project or all of the requester's projects for the specified number of days. Only the requester can view the reason. If access to tasks is blocked temporarily (for example, for 7 days), the history of the Toloker's responses is not saved after the ban is lifted. The skill value is based on new responses. accept all assignments from this Toloker in the pool — Requires the manual review option to be set. Useful if the Toloker 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 and accept all responses in the pool.

Field

Overview

A condition for performing the action in the then field:

submitted task suites — The number of task suites in the pool completed by the Toloker.

then

Action to perform for the If condition:

suspend — Suspend the Toloker's access to the pool for the specified number of days. Only the requester can view the reason.
assign skill value — Assign a fixed value to the skill.
ban — Block access to the project or all of the requester's projects for the specified number of days. Only the requester can view the reason.

If access to tasks is blocked temporarily (for example, for 7 days), the history of the Toloker's responses is not saved after the ban is lifted. The skill value is based on new responses.
accept all assignments from this Toloker in the pool — Requires the manual review option to be set.

Useful if the Toloker 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 and accept all responses in the pool.

Rule example

Task: you're conducting an opinion poll. To collect responses from as many Tolokers as possible, set up the Submitted responses rule.

A Toloker who submits 1 assignment is restricted from accessing the project and can't complete your tasks.

Alert

The assignments submitted by banned Tolokers will be taken into account if they are not rejected using manual review. They can be reassigned by setting up the Recompletion of assignments from banned users rule.

For developers

Troubleshooting

Should I create a skill for every pool?

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

Can one Toloker get access to two pools in the same project? Can I avoid that?

I have two text versions that I want to show to my respondents: one version to half of the audience, and another version to the other half (like in A/B testing). Is this possible in Toloka, or do I need to create two separate projects?

Contact support

Last updated: March 2, 2023

Introduction

Getting started

Important tips

Useful recommendations

Working with Toloka

Projects

Pools

Tasks

Results

Project analysis

Toloka settings

Task interface

Template Builder

HTML/CSS/JS editor

Help and support

FAQ Troubleshooting Support Glossary