> 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/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-faq-list/000007856.md).

# How to switch user accounts on the NextSeq 1000/2000

The NextSeq 1000/2000 is installed with three accounts on the Operating System (OS): **ilmnuser** (standard), **ilmnadmin** (administrator) and **root** (super-administrator). For more information on these account types, see Knowledge Base Article

[User accounts and password management on the NextSeq 1000/2000](https://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000003040.md)

To upgrade the control software, configure network settings, or perform troubleshooting, it is necessary to switch to the **ilmnadmin** administrator account.

**Note**: Only switch user accounts when the system is idle. Switching user accounts while a sequencing run is in progress may result in premature termination of the run.

**How to switch accounts:**

1. From the Control Software main menu, select **Exit Application** to access the Operating System.
2. Click the **power button** from the task bar in the upper right.
3. Select **Log Out** from the dropdown menu to log out of the current account and return to initial user selection screen.
4. Select the **ilmnadmin** administrative account and log in.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-19358832d443bbc5cd2df9ce29b091ad0686d14b%2Fimage1.png?alt=media)

**Note**: Once the administrative tasks are complete, repeat this process to log back into the **ilmnuser** account before performing a new sequencing run.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7856), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007856%20-%20Instrumentation%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/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-faq-list/000007856.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.
