When you open a Task's Assigned To field, wxrks doesn't show you every user in the account — it runs a short list of checks first and only surfaces people who pass all of them. This article explains exactly what those checks are, so you can tell at a glance why a specific person is or isn't showing up. For the click-by-click steps to actually assign someone, see Assigning Tasks to Users.
💡 Who is this for? This guide is for Project Managers and Account Admins who need to understand or troubleshoot who's eligible for a given Task.
The three checks wxrks runs
A candidate has to clear all three before their name appears:
Role — they must hold the Vendor, Project Manager, or Account Admin role. Assignment isn't limited to linguists: a Project Manager or Account Admin with a language pair configured is just as eligible as a Vendor.
Language pair — their profile's Languages tab must include the Task's exact source→target pair. A pair configured the wrong direction doesn't count.
Active status — their account Status must be Active. An inactive user is filtered out even when role and language pair both match, and assigning one manually anyway is silently rejected rather than applied.
On top of those three, the candidate also has to already be linked to the project's Organization or Organizational Unit — covered next.
Why the list is scoped to the project
You don't configure eligibility per Task. Every time you open an assignee field, wxrks runs the checks above live and narrows the results to people already linked to the project's Organization or Organizational Unit — see Accounts, Organizations and Organizational Units for how that link is set. This keeps the dropdown relevant to the project instead of listing every qualifying user in the account, and it's also what stops a Vendor from ever being handed a Task outside the scope they're meant to access.
Manual assignment vs. Auto Task Placement
Everything above is what governs a manual assignment by a Project Manager or Account Admin — only role, language pair, active status, and Organization/Organizational Unit scope matter there. If a project also has Auto Task Placement turned on, eligible Vendors can additionally self-claim unassigned Tasks from Available Projects — but that path stacks several more filters on top: a minimum quality score, tag matching, rate/pricing feasibility, and per-workflow permissions (Translator, Reviewer, DTP, and so on). None of those extra filters apply to a manual assignment; they're specific to self-claiming.
If someone isn't showing up as eligible
Check these, roughly in order of how often each one turns out to be the cause:
Their Languages tab is missing the Task's exact source→target pair, or has it reversed — the single most common cause.
Their account Status isn't Active.
They aren't linked to the project's Organization or Organizational Unit — see Accounts, Organizations and Organizational Units.
They don't hold the Vendor, Project Manager, or Account Admin role.
If you expected them to self-assign through Auto Task Placement instead of being assigned manually, also check their quality score, tags, and rate against the project's settings — see How to use the Auto Task Placement feature.
Related articles
Related article: Assigning Tasks to Users
Related article: How to use the Auto Task Placement feature
Related article: Accounts, Organizations and Organizational Units