> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/disable-or-customize-the-getting-started-page.md). # Disable or customize the Getting started page Disable the Getting started page in Remote Desktop Manager at startup, or replace it with your own custom HTML welcome page instead. When you launch Remote Desktop Manager, the ***Getting started*** page appears by default. If you do not want to see this page each time you open the application, you can disable it in two ways. You can also set a custom welcome page. ### Check Don't show again If you have not closed the ***Getting started*** page yet, check ***Don't show again*** on the right side of the page's toolbar. ### Uncheck Show getting started page at startup In ***File*** – ***Settings*** – ***User interface***, under the advanced ***Other options*** section, uncheck ***Show getting started page at startup***. ### Set a custom welcome page You can choose to show a custom page of your own as the welcome page. Go to ***Administration*** – ***System settings*** – ***Application***, under ***Welcome page***, enable the ***Use web or HTML welcome page*** setting and enter the URL that points to your custom welcome page. --- # 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://docs.devolutions.net/rdm/knowledge-base/how-to-articles/disable-or-customize-the-getting-started-page.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.