> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/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/enate-help/work-manager/work-manager/getting-new-work.md).

# Getting New Work

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM2MTc3MQ==>" %}

Clicking the **Pull from Queue** button in the Work Inbox grid header will assign you a new piece of work, if any is available for you.

![](https://3859925423-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MWYnDNwe3Cuo4zlGbs5%2F-MWqMXrK_ZvY1cj8JBqs%2F-MWqRv4hiUBVt6rGJXr3%2Fimage.png?alt=media\&token=0ae54aa3-e15a-4bc0-afd5-26dc5ed9119f)

### **Pull from Queue Allocation Rules**

**How does the system determine which work item to give a user when they click the “Pull from Queue” button on their Work Inbox?**

The system works by looking at all unassigned work items from all of the Queues the user is linked to, and has permissions on, and assigns one new work item, prioritising items as follows:

1. Any currently OVERDUE work item (most overdue item first). If none found, then
2. Any work item which has been rejected by a Robot. If none found, then
3. Any work item (item due soonest selected first).

{% hint style="info" %}
Note: Queues set to ‘strict mode’ are there to allocate work strictly to robots. Any human users linked to such queues are there only as a fall back for rejected robot work items, and aren’t auto-allocated the normal, unrejected work items from them when hitting “Pull from Queue”.
{% 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 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/enate-help/work-manager/work-manager/getting-new-work.md?ask=<question>&goal=<user_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.
