> For the complete documentation index, see [llms.txt](https://ieg4.gitbook.io/onevu-digital-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ieg4.gitbook.io/onevu-digital-platform/openprocess-cases-and-workflow/openprocess-flex/work-allocation-in-branches.md).
# Work allocation in branches
Whilst each stage of a process can be assigned to a different user or team, there are often use cases where the same user will deal with the whole process or multiple stages of a process.
Right now there is an allocation strategy (rule) that does this called 'Allocate to user from defined previous step'. In this case, the user specifies the step which was previously allocated to a user to set who should be allocated this step.
The problem is, with a branched process some previous steps may not ever be completed because the branch rules mean they're not active in the process. Let's consider the following branched process:
If you had to assign the previous step for the red step on the left in the process, you could technically pick any of possible previous blue steps even though the path to get to the end step may not have touched them.
To remedy this, where OpenProcess Flex is licensed, there is an additional allocation rule called "Allocate to the same user as the step before" as seen below:
This means the step will be allocated to the last active step's allocated user. So in the following we can see when setting the rule for the final red step on the left it would assign it back to the green one and so on:
{% hint style="danger" %}
**IMPORTANT**
1\) Where there is a branch in a process you need to use this allocation strategy. If you attempt to use:
'Allocate to user from defined previous step' on a process with a branch in it you will be unable to select a step.
2\) If you try and save a process, which has a branch, and a step allocation rule set to 'Allocate to user from defined previous step', you will face a validation error.
3\) If you make the **first** stage of a process have the allocation strategy of "Allocate to the same user as the step before" the process will error upon creation so you should **NOT** do this.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ieg4.gitbook.io/onevu-digital-platform/openprocess-cases-and-workflow/openprocess-flex/work-allocation-in-branches.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.