> 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-edms/document-indexing/multiple-indexing-queues.md).
# Multiple Indexing Queues
We originally designed OpenProcess to have a central Document Indexing queue but subsequently sites said that some specialist departments like Benefits have dedicated indexing people.
To cater for this we have the ability to set up different indexing queues by service area.
This is comprised of three functions:
a) A filter (drop down) in the Document Indexing tab to enable the list a user sees to only be the indexing group/service area they're associated with. This is shown below:
b) Within service areas the ability to link a group of users to it for document indexing purposes.
Thus allowing a user to be associated with one or more service areas.
I.e. if a user is in a group and that group is associated with a service area for document indexing then they will see documents ready for indexing in that queue.
{% hint style="info" %}
**Note** that the new System Id also shown in the above screen is used in the configuration of the bulk import tool mentioned next.
{% endhint %}
c) The bulk import tool that takes all scanned documents from a council's server location and moves them to the cloud (OpenProcess) has a parameter (System Id) that should be taken from the Service Area (as seen in the above screenshot) and it is this that ensure imports are be pushed into the appropriate document queue.
Obviously this means the program needs to be run as many times as you have service specific indexing queues.
{% hint style="success" %}
The Bulk Import Process can be run as a scheduled Windows Server Batch process so irrespective of the number of queues, the process can be entirely automated.
{% 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-edms/document-indexing/multiple-indexing-queues.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.