> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-insights/using-insights-for-the-first-time.md).
# Using Insights for the first time
Advanced Insights welcome page
*Applies to: Patch My PC Advanced and Patch Insights*
{% hint style="info" %}
The default credentials for your first logon are below. You will be prompted to change these:
* Username: admin
* Password: 123qwe
{% endhint %}
On first logon, you will see the welcome page. You can access this page any time by clicking your username in the top right of the screen.
The welcome screen needs your Patch My PC license key and your ConfigMgr site server details.
Advanced Insights welcome screen
### License Key
If Advanced Insights is installed on the same server as the Patch My PC Publisher we will read the license key automatically. Alternatively, please add your license key and click to verify.
### Configuration Manager Database Details
Provide the server name and database name of your ConfigMgr primary site and click to connect.
As long as the IIS application pool identity running the Advanced Insights Controller website has permission to read the database, you should be good to go.
If you have a problem at this stage, please see [this document ](/patch-my-pc-insights/insights-sql-permission-requirements.md)for details on granting SQL permissions.
Once the license key and SQL sections are successfully completed, click **Go to Dashboard** in the final step to complete setup.
---
# 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.patchmypc.com/patch-my-pc-insights/using-insights-for-the-first-time.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.
