> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/components/library-file-management/library-file-management-page.md).
# Library File Management Page
To access the library file management page click the avatar in the top right corner and choose **Settings**. Then under **Components** on the left, click **Library files**.
The library files page has three tabs - *Genomic library files, Prep kits files,* and *Other library files*. This section of the user guide will focus on the *Genomic library files* tab, which is relevant for next-generation sequencing analysis (Figure 1).
The **arrows** ( v / .png?alt=media)
) expand/collapse each section. Associated library files are shown in a table in each section. In the *Actions* column of each table, the  **View library file details** button displays additional library file details, the **bin** () icon dissociates a library file. The hourglass () icon indicates a library file is being created.
## Additional Assistance
If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.
---
# 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://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/components/library-file-management/library-file-management-page.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.