Auto Task Placement lets eligible Vendors see and claim available Tasks themselves, instead of a Project Manager assigning every one by hand. It's built from several independent pieces — two on/off switches, a set of matching filters, a per-vendor workflow selection, and an optional notification setup — and missing any one of them is the most common reason a vendor sees no Tasks at all. This guide walks through every piece, for both the person configuring it and the vendor using it.
​

💡 Who is this for? This guide is for Account Admins setting up automatic Task-to-Vendor matching, and Vendors claiming Tasks through it.

When Auto Task Placement is on for a project, any Task that isn't manually assigned becomes visible under Available Projects to every Vendor who clears the filters below — language pair, quality score, tags, and a few others. The Vendor claims it themselves with I Want it!; nobody assigns it to them first.
​
That's a different, stricter bar than manual assignment, which only checks role, language pair, and active status — see Task Assignment Eligibility Rules for those checks and Assigning Tasks to Users for the click-by-click steps. Auto Task Placement stacks everything below on top of that baseline.

There are two independent switches, and both matter — the Organizational Unit switch only sets a default for new projects going forward. It doesn't retroactively enable the feature on projects that already exist.

Open the Organizational Unit, go to its General tab, click More settings, and turn on Auto Task Placement. Every project created under this Organizational Unit from then on will have it enabled automatically. Click Save to apply it.

On an existing project's Overview tab, click More Info to reveal the Auto Task Placement switch. This is the setting that actually decides whether the project's unassigned Tasks become claimable right now — it takes effect immediately, no separate save step. Only a Project Manager or an Account Admin with the Auto-Assign Tasks permission sees it.

Every user with the Vendor role is granted the Auto-Assign Tasks permission automatically as part of that role, and it can't be turned off for them individually. You can see it — but not disable it — on a user's Permissions tab, under the TASK category.

Having the permission isn't enough by itself. Each Vendor also needs to be opted into the specific workflows — Translation, Review, Proofreading, DTP, Voiceover, and so on; see Managing Your Custom Workflows for what a workflow step actually is — they're qualified for. Open the Vendor's user profile and go to the Auto Task Placement tab, visible only to an Account Admin editing someone else's profile, to select which of the account's workflows this Vendor can receive.

A Vendor with no workflows selected here won't be offered anything through Auto Task Placement, regardless of how the filters below are configured. They'll also still need the Task's language pair on their own Languages tab — see Task Assignment Eligibility Rules for that requirement.

The filters that decide which vendors qualify for a claimable Task live under Settings > Automation Settings, on the Auto Task Placement Settings tab. These set account-wide defaults; several can be overridden per Organizational Unit, and one can be overridden per Task (covered further down).

1. Quality filter — scores a vendor's previous work from 0–100% and only lets vendors above the Minimum Translator Score (default 60%) see the Task. For a vendor with no completed wxrks jobs yet, it's usually worth leaving this off until they've built up a score. A separate Minimum Translator Score to Skip Review slider lets a high-scoring translator's work skip the review step entirely — with a 60% minimum and a 90% skip-review threshold, for example, a vendor at 75% can claim the Translation Task but their delivery still goes through review, while a vendor at 92% skips that review step.
​
​2. Rate filter — requires a vendor to have Word Rate data on file for the language pair (from the price list or a Stop Loss value) before they're eligible.
​
​3. Tag filter — requires a vendor to share at least one tag with the project. If neither side has tags, this filter has no effect.
​
​4. Acceptance Checklist — shows a claiming vendor a checklist of conditions they must acknowledge before the claim goes through (shown in What the vendor sees below).
​
​5. Minimum number of jobs performed to Skip Review — pairs with the Skip Review score above: a vendor also needs at least this many completed jobs (up to 100) before their work can bypass review.

⚠️ Disabling all workflow options for a vendor (see Choosing which workflows a vendor can see above) blocks self-assignment for them entirely, no matter how these filters are set.

Below the filters, Assignment Rule controls how many workflow steps of the same file a vendor can claim in a row:

Below these account-wide settings, a table lists every Organizational Unit and Account with columns showing whether its Quality, Rate, and Tag filters are currently Enabled or Disabled. Click a row to override that Organizational Unit's filters instead of inheriting the account default.

To adjust Auto Task Placement for one Task rather than a whole project, open the project's Tasks tab, open that Task's row menu, select Details, then the Auto Task Placement tab.

1. Minimum score required — overrides the account-wide Minimum Translator Score for this Task only. Leave it at 0 to fall back to the account or Organizational Unit setting.
​
​2. Assignment Log — a read-only summary of how the Task is doing: how many linguists are currently Eligible, how many Viewed it, and how many Rejected it.

Vendors don't have to keep checking Available Projects manually — wxrks can email them when new matching Tasks appear. Two switches control this, and both have to be on for a given vendor to actually receive anything.

Open the Organizational Unit's Notifications tab and turn on Enable Email Notifications For Available Tasks. This authorizes notifications for every Task created under that Organizational Unit; without it, nobody linked to it receives available-Task emails, whatever they choose on their own profile.

From their own profile's Notifications tab, a vendor turns on Enable Tasks Available Email Notification and picks when to hear about it — nothing goes out until a schedule is set:

1. Select days to be notified — with no day selected, no emails go out at all.
​
​2. Choose your quiet hours — an optional time range during which emails are held back even on a selected day.

Each email lists up to the top three available Tasks, so a vendor never gets more than one email's worth of noise at a time.

Once everything above is configured, matching Tasks appear under the vendor's Available Projects tab. They select what they want and click I Want it! to claim it.

If the Acceptance Checklist filter is on for the project, claiming shows this checklist first — every item must be checked before the vendor can confirm with I got it!:

For the rest of a vendor's day-to-day — translating, delivering, getting paid — see Vendor's Quick Guide and Vendor's Portal.

Related article: Task Assignment Eligibility Rules
​Related article: Assigning Tasks to Users
​Related article: Managing Your Custom Workflows
​Related article: Vendor's Quick Guide
​Related article: Vendor's Portal