> 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/icm/analyses/analysis-functionality/settings/pipeline-management.md).
# Pipeline management
The *Pipelines* management page allows users to view and manage all pipelines created in the domain. Within Analysis, user can create a pipeline from a specific type of data, it will be listed in this management page. To access the page, click the gear button on the top right corner, choose **Settings**, then select **Pipelines** on the left.
## Downloading a pipeline
To download a pipeline, click the **Download pipeline** in the *Actions* column. A file with the extension \*.pipeline will be download to the default download directory of your local computer.
## Importing a Pipeline
Within the Pipeline management page, you can upload a pipeline from your local computer. You can import a pipeline even before you create an analysis.
### From My Computer
1. To import a .pipeline file from your local machine, click on the **+ Import pipeline** button on the *Pipelines* management page
2. Click the **+ Choose** button
3. Browse to the location of the .pipeline file on your local machine and select it for upload. The selected file name will be displayed next to the *Choose pipeline* button
4. If you wish to give the pipeline a new name, type a new name into the *Rename pipeline* box and click **Import**
---
# 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/icm/analyses/analysis-functionality/settings/pipeline-management.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.
.png?alt=media)
.png?alt=media)