Ban
Tolokers can be banned in two ways:
How to ban a Toloker
You can block a Toloker's access to one or more projects. This lets you control manually which Tolokers will complete tasks. For example, you can choose all Tolokers with a skill value lower than N and block their access to tasks. You can also unblock access.
Warning
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.
In the interface
To block access to tasks for a single Toloker:
-
Select a Toloker on the Tolokers page.
-
Click Actions → Ban, then fill in the fields:
Field
Overview
Ban type
Where to apply the ban:
- In all my projects — All projects.
- In the project — A single project (choose one from the list).
Ban expires
Set when to lift the ban.
We recommend blocking access temporarily in order to maintain the desired number of Tolokers for completing tasks.
Reason
The reason for banning (only seen by the requester).
To block access to tasks for multiple Tolokers:
-
Select Tolokers by using the filters on the Tolokers page or upload a TSV file:
<annotator id 1> <annotator id 2> ... <annotator id n> -
Click Ban, then fill in the fields (see the table above).
You can view information about access to tasks on the Toloker's page (on the Tolokers page, go to the Bans tab). To unblock access to tasks, hover over the ban line and click .
How to work via Toloka API
To block a Toloker's access using Toloka API, send a PUT request with the information about the ban:
curl -X PUT 'https://toloka.dev/api/v1/user-restrictions' \
-H 'Authorization: OAuth AQC2AGAJgyNSA8CtpdO9MWy_QEB6s6kDjHUoElE' \
-H 'Content-Type: application/json' \
-d '{"scope":"ALL_PROJECTS","user_id":"1ad097faba0eff85a04fe30bc04d53db","will_expire":"2030-01-01T00:00:00.000Z"}'
Refer to the Block access to tasks section of the Toloka API documentation for more details about the request, its parameters, and possible responses. You will find examples of the requests in Toloka-Kit and other code samples there.
Banning on the platform
Toloka has dedicated anti-fraud system for banning dishonest Tolokers. It monitors user behavior and blocks suspicious accounts.
The main reasons for banning:
- Disclosure of confidential information.
- Using scripts and bots or any form of cheating.
- Poor response quality.
- Providing false data during registration.
- Frequently skipping captchas or entering them incorrectly.
- Using multiple accounts.
- Location cheating.
Note
If a Toloker's behavior seems suspicious, write to support. We'll conduct an additional review. If the Toloker is violating the user agreement, they'll be blocked in the system and will no longer be able to complete tasks.
You can also ban this Toloker from your project.
For developers
Troubleshooting
Unfortunately, this Toloker has violated the user agreement and will no longer be able to complete tasks. You can find new Tolokers or customize filters so that they better match the project requirements.
You can deny access to the pool if the Toloker's responses are too fast, if they don't match the majority vote, or if the Toloker makes too many mistakes in control tasks. Tasks completed by such Tolokers can be given to other Tolokers.
No. After sending a task, the Toloker can't make any changes to it. You can add tasks that were completed incorrectly to a new pool.
No, you can't fix anything in the task itself. However, you can do this manually in the results file.
Fraudulent Tolokers aren't banned before the majority vote is known. That's why we recommend that you have new Tolokers complete training or a test. Then you can select the Tolokers that successfully completed the training to do your tasks.
If the Toloker was already paid for the tasks, you can't cancel the payment.
During the training, Tolokers follow the task instructions and practice completing your tasks. Based on the training results, the requester can select Tolokers who did well enough to get access to the main pool. However, the mere fact that the Toloker completes your training pool successfully does not guarantee that they will continue to demonstrate high-quality performance. Tolokers who did well on the training but had inadequate results in the general task might have obtained correct training responses from other people.
In addition to the training, be sure to set up quality control rules in your main pools. This lets you control the quality throughout the task completion process. If the task requires that users send free-format responses or data files, use manual review to pay for them only after reviewing the responses.
The results show the responses of all users, including those who are banned. To exclude their responses from the results, select the option Exclude assignments by banned users. It will delete the responses from users who were banned at the moment the results were downloaded, not when the pool was labeled.
You can't automatically reject the responses of a banned Toloker.
But you can do it yourself if you want. When downloading the results, select the option Exclude assignments by banned users to delete the responses of Tolokers who were banned at the moment of downloading. You can also forward all the assignments from banned users to other Tolokers using the Re-completion of assignments from banned users rule.