Skip to main content
Task Assignment Rules
Updated over a week ago

This article explains the dynamics of allocating Vendors to Tasks. To learn about Accounts structure, please refer to this article: Accounts and Organizations


The process for allocating Tasks in a project is based on the Vendor links to Organizations and Organization Units. Thus, a Vendor will only be able to be allocated to a Task if it belongs to the Organization or Org Unit to which the project is linked, guaranteeing that there is no security problem characterized by the allocation of a Vendor that should not have access to that content.

  • Consider the example below to illustrate this dynamic:

In this example, following the hierarchical order, we have:

  1. First tier: Organizations 1 and 2

  2. Second tier: Organizational Units 1, 2, 3 and 4

  3. Third tier: Projects 1, 2, 3 and 4, each with only one Task for simplification

- If Translator A is linked to Org Unit 1 and Organization 2, he can be allocated to Tasks 1, 3 and 4:

- If Translator B is only linked to Organization 2, it can be allocated to Tasks 3 and 4:

- If Translator C is bound to Org Unit 3, it can only be allocated to Task 3:

- If Translator D is linked to Org Unit 2 and Org Unit 4, it can only be allocated to Tasks 2 and 4:

So, let's validate this inside Bureau Works?

We know that, in Bureau Works, you assign tasks to translators through the project's panel. Differently from the diagrams above, where we have a flow in which we are "accessing" the translators to see which tasks are available to be assigned, in Bureau Works it goes the other way around: you must access the tasks to assign the translators that are eligible for the work.

So, to illustrate it even more, let's flip things a little bit and reproduce all four situations in the system.

We see that Task 1 is only available to the Translator A, since it's the only one linked to Org. Unit 1 and there's no other vendor associated with Organization 1 either.

Opening Task 1 in the System, we will notice that, in fact, the Translator A is the only one available.

Same goes with Task 2. Since Translator D is the only one associated with Org. Unit 2, and there are no other Translators associated directly with Organization 1, Task 2 it's only available for Translator D.

Opening Task 2 in the system, we see that Translator D is the only translator available too:

As for Task 3, we have that it's associated with Org. Unit 3, which is subordinate to Organization 2. This means that Translators associated with Org. Unit 3 or Organization 2 will be eligible for this task.

Opening Task 3 in the system, we have the following situation:

Finally, for Task 4, it will be eligible for every Translator associated with Org. Unit 4 or Organization 2.

Opening Task 4 on the system, there's the situation:

Did this answer your question?