> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/basespace/sequence/plan-runs/prep-tab/import-biosamples-prep-tab.md).

# Import Biological Samples

{% hint style="warning" %}
The Prep tab is deprecated and no longer available. For run planning and sequencer integration, see the [Run Planning](/basespace/sequence/plan-runs.md) section.
{% endhint %}

## Import Biological Samples

Use the following steps to import biological samples from an external .csv file.

1. From the runs page, select New Run, and then select Prep Tab.
2. From the Prep page, select Biological Samples.
3. Select Import.
4. \[Optional] Create a .csv file as follows.
   1. Select the spreadsheet image to download a template.
   2. Complete the following fields for each sample:
      * Sample ID—Enter a unique sample ID.
      * Name—Enter a descriptive name for the biological sample.
      * \[Optional] Species—Enter the appropriate species.
      * Project—Enter the name of the project to save samples to. The selected project is the default project that contains biosample data output.
      * Nucleic Acid—Enter RNA or DNA.
   3. Save the file.
5. Select Choose .csv File.
6. Browse to the appropriate file and select Open. Information from the .csv file populates the Biological Samples page.
7. \[Optional] Select additional samples as follows.
   1. Select Save & Continue Later.
   2. Select the checkbox for each sample you want to use.
8. Select Prep Libraries.


---

# 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.connected.illumina.com/basespace/sequence/plan-runs/prep-tab/import-biosamples-prep-tab.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.