> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/understand-your-business/ai-features/service-display-monitor-getting-started/service-display-monitor-logging-in-and-authentication.md).
# Service Display Monitor: Logging in and Authentication
The [Service Display Monitor](/docs/understand-your-business/ai-features/service-display-monitor-getting-started.md) (SDM) requires authentication on first login, in addition to **every time it reboots** and each **90 days thereafter**.
The authentication process requires scanning a new QR code and entering login credentials.
## How to Authenticate and Login to the SDM
To authenticate the SDM:
1. Navigate to .
2. Scan the QR code on this website with your mobile phone.
3. Proceed with the prompts as they are presented on your phone.
4. You will be prompted to login. Your customer success representative will provide you with a username and password at this point.
5. You may disconnect the keyboard and mouse and store it in a safe place for future use once successfully logged in.
**Note**: For security reasons you will be required to re-login every 90 days. Please retain the supplied credentials in a convenient location.
---
# 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://help.solink.com/docs/understand-your-business/ai-features/service-display-monitor-getting-started/service-display-monitor-logging-in-and-authentication.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.