> 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/basespace-cli/software-basespace-cli-reference_material-list/000008347.md).

# How to authenticate the BaseSpace Command-Line Interfact (CLI) to a workgroup

When using the BaseSpace Command-Line Interface (CLI), the `bs auth` command creates a default configuration profile that will be used each time the `bs` command is invoked. This configuration can be used with a personal workgroup, a professional workgroup, or an enterprise workgroup.

To set either a professional or enterprise workgroup as default configuration, log into the desired domain and/or workgroup on BaseSpace prior to pasting the link into the browser. The `bs auth --force` command may be needed if the user has already authenticated the personal account. This command overwrites the current config and set the workgroup as default config. Copy the URL generated and paste into a browser, then accept the authentication request.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-47cec158fa4f589b753bb3b3a5387d9b218ee87e%2Fimage1.png?alt=media\&token=7c07b9bf-8595-466c-8d2e-1a0de94527f8)

Alternatively, to keep the default config and create a separate config for a workgroup or vice versa, use the `-c {configname}` option to generate a separate configuration file. This allows the use of two or more configuration files without needed to reauthenticate each time a different BaseSpace User context is needed. Then when running commands, they also must include the config flag, such as:

`bs -c {configname} uploadbs -c {configname} whoami`

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-7609a34d6654dd6790ddf04b7f2fd49fca2f8758%2Fimage2.png?alt=media\&token=2ed8a991-7d2a-4d3f-a544-5bfd333dba08)

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-e866e2630ee167d57cfc16e4dc000dda26ea88ea%2Fimage3.png?alt=media\&token=9728a4c3-2e67-44a2-8948-ed61e10267be)

For further information, see the [CLI overview](https://developer.basespace.illumina.com/docs/content/documentation/cli/cli-overview#authenticate) page.

\
\
\ <br>

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