> 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/2022.4-changes-overview/work-reassigning-improvements.md).

# Work Reassigning Improvements

We have added an additional setting in a [member's user profile](https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/home-page/team-bar/team-bar-for-team-leaders#viewing-an-individual-user) (accessible by Team Leaders) which allows Team Leaders to modify their Team Members' ability to work solely on items which are specifically assigned to that user's Queues.&#x20;

![](/files/3YveLxpb5qZRXZsdYbQk)

They will still be able to get more work via the 'Pull from Queue' button as per usual (as this approach only ever allocates work to a user from their Queues anyway). However, it will stop work from a different Queue to the user from being manually reassigned to them by one of their peers.

When the setting is off, they are able to work on items assigned to any Queue (with the bounds of the permissions set for them in Builder via their User Group Permissions).

When the setting is switched on, the user will still be able to work on items that are not assigned to a Queue. Additionally, if there are some work items *already assigned* to the user that are in Queues they're not part of, the user will still be able to continue working on them, but assigning any further work items to them from outside of their Queues will now be blocked. You can unassign these work items from the user manually.&#x20;

Furthermore, if one of the work items already sitting with the user (but outside of their Queues) enters a state of Waiting or Resolved, it will move to the Team's Owned Work and will be unassigned - and its owner will be cleared. Once that work item is ready to be processed further (e.g. because new information has come in for it), it will NOT be assigned back to the original assignee, since they are no longer part of its Queue; it will instead be assigned according to allocation rules.


---

# 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://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.4-changes-overview/work-reassigning-improvements.md?ask=<question>&goal=<endgoal>
```

`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.
