> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/v19-en-us/parallels-ras-19-administrators-guide/parallels-web-client-and-user-portal/configure-themes/web-client-settings/branding.md).

# Branding

The **Branding** category allows you to configure the branding of User Portal.

The following properties can be customized:

* **Webpage title:** Specifies the title that appears on the webpage. You can type any title you like.
* **Login to:** Specifies a name that will appear in the User Portal login dialog. For example, if you type "ABC" here, the login page will say, "Log in to ABC". There are two predefined variables that you can use here: %FARM% (the actual Farm name; this is the default value) and %SITE% (the Licensing Site name).
* **Company logo:** Displays the image which is displayed on the User Portal page header. To change the image, select browse and then specify the image file. Note that changing the logo image also removes the default **Remote Application Server** part from the page header.
* **Favicon icon:** Displays the currently set favicon icon. To change the icon, click **Browse** and select an icon file.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-admin-guide/v19-en-us/parallels-ras-19-administrators-guide/parallels-web-client-and-user-portal/configure-themes/web-client-settings/branding.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.