> 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/software/cloud-software/software-cloud-software-reference_material-list/000001847.md).

# How to set the default location for uploaded runs to BaseSpace

Each BaseSpace account has a Personal Workgroup that is the default location for run uploads when using that account to sign into BaseSpace from an instrument’s control software. If an account is associated with a Professional or Enterprise Workgroup, the Default location for uploaded runs can be changed to send data to a different Workgroup. This enables easy collaboration by sending data to a Workgroup accessible by multiple users and allows Professional/Enterprise users to take advantage of the option to store data beyond the free 1 TB by sending to a non-Personal Workgroup.

*Note: This setting also dictates which runs planned in Preptab will be visible while logging into BaseSpace on a NextSeq 500/550 (pre update to Control Software v4.0) or MiniSeq (pre update to Control Software v2.0). Runs planned under the Personal Workgroup will only be visible in the control software if the 'Default location for uploaded runs' is set to 'Personal'.*

**To change the default workgroup:**

1. From the main BaseSpace page, select the name on the top right of the screen and select Settings.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-728b61da7ef9e29fb07904489c5dd77974c54571%2Fimage1.png?alt=media\&token=6bc5dc1c-b4d1-46d9-8dc8-41267b9b3670)
2. While on the Account Overview section of settings select the dropdown menu under “Default location for uploaded runs.”\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-6b09589220fcba7b79ca5abd5634e30c6b838cfc%2Fimage2.png?alt=media\&token=d32c1155-d7f1-4be4-b16f-09323fc3b26c)
3. Select the desired Workgroup from the list and the settings will be automatically saved.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-7f270dcca69b90c37455cfdf7e7747a79c641a93%2Fimage3.png?alt=media\&token=1db5a153-1f1d-4ca2-b674-c92f0ab918d9)
4. All future runs will now be uploaded to the selected Workgroup when that account is used to sign into BaseSpace on an instrument.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                 |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1847), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001847%20-%20Software%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/software/cloud-software/software-cloud-software-reference_material-list/000001847.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.
