> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000008929.md).

# How to import a pre-existing index kits into Local Run Manager v3 and v4

In some cases, new index kit offerings will be made available for existing library preparation kits. Index kit files (pre-existing index kit files) can be added to existing Library Prep kit options in Local Run Manager. Use the steps below to import a pre-existing index kit into Local Run Manager (LRM) v3 or v4.

1. Save the desired index kit locally on the instrument.
2. Open Local Run Manager by navigating to <https://localhost/#/> via the Chromium Web Browser on the instrument.
3. Select **MENU**.
4. Select **Tools**.
5. Select **Index & Library Prep Kits**.
6. Select the tab for **Index Kit**.
7. Select **Add Index Kit** on the right-hand side.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-90c617f3e7d3e248f34d4a9097d987aee439c9ed%2Fimage1.png?alt=media)

7. Browse to the index kit saved on the instrument and select **Open**.

For information on creating a custom library prep kits/index kits to import into Local Run Manager v3 and v4, see Knowledge article[How to use custom library prep and index kits with Local Run Manager v3 and v4](/software/local-run-manager/software-local-run-manager-reference_material-list/000005897.md).

If additional assistance is needed, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #8929), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000008929%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000008929.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.
