> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.1-changes-overview/allocation-method-changes.md).
# Allocation Method Changes
The allocation method 'From Team By Path' has been removed.
We have added two new allocation methods which lets you allocate work to an individual from a specific User Group:
1. **Individual from User Group** will allocate a work item to an individual in the selected User Group based on a round robin basis i.e. user 1, then user 2, then user 3, then user 1 etc.
2. **Individual from User Group (by capacity)** will allocate a work item to the individual in the selected User Group who has the lowest amount of estimated hours of work in their inbox
{% hint style="info" %}
Migration from the 'From Team By Path' allocation method will happen automatically. Upon upgrading to version 2023.1, any processes using the allocation method 'From Team By Path' will be updated to use the allocation method 'Individual from User Group (by capacity)'. Members in the 'Team' of the 'From Team By Path' allocation method will be migrated to a new User Group with the name 'Migrated for allocation - \[Team name]'.
{% endhint %}
See here for further information about how to use allocation methods in Enate:
{% embed url="" %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.1-changes-overview/allocation-method-changes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
