> 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-mp-guide/infrastructure/site-defaults.md).

# Site defaults

The Site defaults category allows you to configure default settings for various RAS components and services. At the time of this writing, you can configure Site defaults for the following:

* **Publishing** — See [**Site defaults (Publishing)**](/landing/ras-mp-guide/publishing/manage-published-resources/site-defaults-publishing.md).
* **Gateways** — See [**Configure a Gateway**](/landing/ras-mp-guide/infrastructure/gateways/configure-a-gateway.md).
* **RD Session Hosts and Host pools** — see [**Agent Settings**](/landing/ras-mp-guide/infrastructure/rd-session-hosts/configure-an-rd-session-host/agent-settings.md).
* **Multi-factor Authentication** — see [**Multi-factor authentication**](/landing/ras-mp-guide/site-settings/multi-factor-authentication.md).

When you add a component to a RAS Farm, or when you publish a resource, Site defaults are used so you don't have to enter the values manually every time. You can easily override the defaults with your own values if necessary.

To view Site defaults, click any of the available categories. To modify the default settings, click **Edit** in the Site defaults view.


---

# 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.parallels.com/landing/ras-mp-guide/infrastructure/site-defaults.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 `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.