> 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-500-550/instrumentation-nextseq-500-550-reference_material-list/000002088.md).

# How to create Local Run Manager credentials to perform a NextSeq 500/550 system check in NCS 4.0.X

An admin account for Local Run Manager (LRM) is required for users to use the NextSeq Service Software (NSS) to perform a system check. User management is required for LRM version 4 (NextSeq Control Software v4.2). However, on LRM version 2.X (NextSeq Control software 4.0.X), user management is optional.

On LRM version 2.X, users can create their own Local Run Manager (LRM) login credentials to enable user management in LRM. After creating the new LRM login, the user can use the new admin level account and log into the NSS to run the required system checks. This can be done through the following steps:

1. In LRM, navigate to **Tools** and then select **User Management**.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-a56ac515f680ac4e847aefbd91ca35897e617da8%2Fimage1.png?alt=media\&token=ab0c15fc-67ea-497d-b0e3-4611ac299a1a)
2. Select **Enable**.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-a319ccc2bccfe3878884cb4be21171a698023188%2Fimage2.png?alt=media\&token=d513f497-c8c4-43e4-a6cb-53a538a25c8e)

3. Create a new user with an Admin level account.

**Note**: a temporary password will be created and the user will be prompted to update the password. ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-6c6717504fbe21a9db8f9177b83cf1ef1dee9de0%2Fimage3.png?alt=media)

**Optional**: The user can disable **User Management** if desired.

\
\
\ <br>

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