> 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-cloud/custom-apps/create-a-custom-app/custom-apps-general-information-tab.md).
# Custom Apps "General Information" tab
*Applies to: Patch My PC Cloud Custom Apps*
### Configure General Information
The **General Information** tab is where you configure the basic information for the Custom App:
1. To upload an icon for the app either:
1. Click **Upload Icon** to upload a suitable file (png, jpg or jpeg) to use as the icon for this app.
2. Drag and drop the image file onto this page.
2. In the **App Name** field, enter a unique name for the app.
{% hint style="info" %}
**Note**
If you specify a version number in this field, we will remove it, as this field does not get updated whenever you add a new version. Also, if you need to use non-ASCII characters, use the "`%`" character instead.
{% endhint %}
3. In the **Vendor** field, either select an existing entry from the dropdown or enter the required name.
{% hint style="info" %}
**Note**
If the vendor is new to your portal, you will see the **Success – The vendor <*****vendor\_name*****> has been created** notification. The next time you add an app, this vendor will appear in the **Vendor** dropdown.
{% endhint %}
4. In the **Description** field, enter a description of the app.
5. Enter any optional internal notes, then click **Next** to move to the [Configuration ](/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-configuration-tab.md)tab.
---
# 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-cloud/custom-apps/create-a-custom-app/custom-apps-general-information-tab.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.
