> 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/general/instrumentation-general-reference_material-list/000007828.md).
# How to cache credentials for access to Network Storage and verify Read/Write access
**Cache Network Storage Credentials**
In order to configure a Windows account with persistent access to Network Storage locations, it is necessary to cache the network storage credentials within the Windows account using the following steps.
1. Login to the instrument using the Windows account(s) which will be writing to network storage (typically **sbsuser**).
2. Open **File Explorer** and enter the network output location (in UNC format) into the address bar.\
3. Enter the credentials of the desired user who has access to the desired network storage location into the Windows Security prompt. You may need to work with your IT team for assistance with these credentials.
4. Select **Remember my credentials**, then select **OK**. This will add the network storage credentials to the Windows **Credential Manager.**\
5. Open the **Credential Manager** application in Windows. Verify that the credentials entered above have been cached to in the Windows Credentials. **Note**: If these credentials change, the cached credentials must be updated in order to continue output to your network storage. 
**Verify Write access to Network Output Location(s)**
1. In Windows **File Explorer**, right click within the intended Network Output location and select **New** > **Text Document** to create a new document called test.txt. 
2. Delete the file just created.
3. If either of the actions above fails, your account does not have write permissions on the Network Output location. Work with your IT team to configure the Network Output location with appropriate permissions.
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7828), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007828%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/general/instrumentation-general-reference_material-list/000007828.md?ask=&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.