By default, when a project manager assigns a task to a vendor, that task becomes the vendor's work immediately — status Assigned, no questions asked. Assignment Acceptance changes that: the assignment becomes an offer. The task sits in Pending Acceptance until the vendor explicitly accepts it, and if the vendor rejects it, the task returns to the pool and the project manager is notified.

This article covers the whole loop: turning the setting on, tuning it per Organizational Unit, customizing the emails, and what each role sees once it's live.

Permission names above are the ones shown to Account Admins in People > Users > [User] > Permissions. For what each of the four wxrks roles can do in general, see All About wxrks Roles.

ℹ️ Note: An Organizational Unit is the client-level container a project belongs to; every project in wxrks sits under exactly one. That matters here because Assignment Acceptance is resolved per Organizational Unit, not per project.

A task only goes to Pending Acceptance when all four of these are true at the moment of assignment:

If any one of them is false, the task goes straight to Assigned, exactly as it did before this feature existed.

The account-level switch is the baseline for every Organizational Unit that doesn't set its own value.

⚠️ Warning: This is not a soft default — saving the account switch writes the same value into every Organizational Unit in the account, overwriting whatever each unit had before. If you had already tuned individual units, that work is lost. Turning the account switch off cascades the same way, and in that direction wxrks doesn't show the confirmation dialog at all. Always set the account switch first, then adjust individual units (Step 2).

Use this when one client needs a different rule than the rest of the account — for example, a demanding client whose vendors must confirm every assignment, while the rest of your work is committed directly.

ℹ️ Note: When a task is assigned, wxrks reads the setting from the project's Organizational Unit first. Only if that unit has no value stored does it fall back to the account. If neither has a value, Assignment Acceptance is off. Because Step 1 stamps a value onto every unit, the fallback normally only applies to units created before the account switch was ever touched.

wxrks sends usable default emails, so this step is optional — do it when you want your own wording, subject line, or branding.

Three templates cover this workflow:

To edit one:

💡 Tip: REJECTION_REASON is only available in the Task Pending Acceptance Rejected template — it's the vendor's own note. Include it in the body so your project managers see why an offer was turned down without having to open the task.

ℹ️ Note: The two vendor-facing emails also depend on the Organizational Unit's Send Notification Emails To Vendors switch, on the Org. Units tab of the same Notifications page. If that's off for a unit, its vendors still see offers in the platform, but receive no email about them. The rejection email to the project manager is not affected by that switch.

Assigning doesn't change. Follow Assigning Tasks to Users for the click path — single assignment, bulk assignment, and bulk task updates all work the same way. Whether a given vendor is allowed to be assigned at all is a separate question, covered in Task Assignment Eligibility Rules.

What changes is the result. Instead of Assigned, an eligible task lands in Pending Acceptance, and the vendor is emailed.

To find these tasks:

ℹ️ Note: Only tasks currently in Pending change status on assignment. Reassigning a task that is already Assigned to a different vendor does not send it back through the acceptance step.

Offers are grouped by project, workflow step, and target language. Each group row shows the project name, its reference, the Organizational Unit, the workflow, the Pending Acceptance badge, the project due date, source and target languages, and how many tasks the group holds. Use the filter above the table to narrow by name, workflow, source language, or target language, and the sort control to order by due date, number of tasks, workflow, or language. If nothing is waiting, wxrks shows No tasks are waiting for your decision.

Accepted tasks move to Assigned, leave this tab, and appear under My Projects as normal work.

💡 Tip: Check the Payable Amount and Due Date before accepting. Once you accept, the task is committed to you — there's no Reject button on an assigned task, and returning it means asking the project manager to unassign you.

Rejecting is immediate and unassigns you: the task returns to Pending, it leaves your Pending Acceptance tab, and the project manager receives the Task Pending Acceptance Rejected email with your reason. The project manager can then offer the task to someone else.

⚠️ Warning: You can't undo a rejection yourself. Once the task is back in Pending, only a project manager or admin can assign it to you again.