> 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/powershell-universal/config.md).

# Configuration

- [Agent](https://docs.devolutions.net/powershell-universal/config/agent.md): Configure PowerShell Universal Agents to run scripts on remote machines over WebSockets using agent.json connections without PowerShell Remoting.
- [App Settings](https://docs.devolutions.net/powershell-universal/config/settings.md): Configure PowerShell Universal application settings in appsettings.json, covering Kestrel endpoints, authentication, JWT, and data persistence.
- [Best Practices](https://docs.devolutions.net/powershell-universal/config/best-practices.md): Follow PowerShell Universal best practices for environments, caching, API design, job output, app performance, and production hosting reliability.
- [Branding](https://docs.devolutions.net/powershell-universal/config/login-page.md): Customize PowerShell Universal branding, including colors, images, copyright text, and admin console title through the Branding settings page or branding.ps1.
- [Command Line Options](https://docs.devolutions.net/powershell-universal/config/command-line-options.md): Launch Universal.Server.exe with command line options in PowerShell Universal to load a custom appsettings file or start the server in demo mode.
- [Deployments](https://docs.devolutions.net/powershell-universal/config/deployments.md): Package and version PowerShell Universal configuration repositories as immutable deployments, then apply and pin them across a cluster of nodes.
- [Environments](https://docs.devolutions.net/powershell-universal/config/environments.md): Configure PowerShell Universal execution environments, including Integrated, PowerShell 7, Windows PowerShell 5.1, and minimal custom environments.
- [Feature Flags](https://docs.devolutions.net/powershell-universal/config/feature-flags.md): Disable unused PowerShell Universal features like APIs, terminals, dashboards, or published folders using feature flags to reduce attack surface.
- [Git](https://docs.devolutions.net/powershell-universal/config/git.md): Sync PowerShell Universal configuration with a remote git repository, covering branches, authentication, sync behavior, and conflict troubleshooting.
- [Hosting](https://docs.devolutions.net/powershell-universal/config/hosting.md): Host PowerShell Universal as a Windows Service, in IIS, in Azure, or standalone, and configure Kestrel ports, HTTPS certificates, and security headers.
- [Azure](https://docs.devolutions.net/powershell-universal/config/hosting/azure.md): Deploy PowerShell Universal to Azure using container web apps or standard web apps, configuring persistence, SQL storage, and forwarded headers.
- [High Availability](https://docs.devolutions.net/powershell-universal/config/hosting/high-availability.md): Configure PowerShell Universal high availability using SQL persistence, load balancers, and one-way git sync across multiple clustered nodes.
- [IIS](https://docs.devolutions.net/powershell-universal/config/hosting/hosting-iis.md): Host PowerShell Universal in IIS by configuring the application pool, website bindings, web.config settings, and Windows Authentication for jobs.
- [Reverse Proxy](https://docs.devolutions.net/powershell-universal/config/hosting/reverse-proxy.md): Configure PowerShell Universal to run behind a reverse proxy, covering WebSocket support, forwarded headers, and Azure Application Proxy setup.
- [Management API](https://docs.devolutions.net/powershell-universal/config/management-api.md): Use the PowerShell Universal Management API to automate admin console actions via REST calls, the Universal module, and app token authentication.
- [Module](https://docs.devolutions.net/powershell-universal/config/module.md): Connect to PowerShell Universal with the Universal PowerShell module, covering Connect-PSUServer authentication, scopes, and security models.
- [Persistence](https://docs.devolutions.net/powershell-universal/config/persistence.md): Configure PowerShell Universal data persistence with SQLite, SQL Server, or PostgreSQL, including database sizing, troubleshooting, and reclaiming disk space.
- [psu Command Line Tool](https://docs.devolutions.net/powershell-universal/config/psucli.md): Use the psu command line tool in PowerShell Universal to reset admin passwords, convert or migrate databases, and clone, pull, or push git repositories.
- [Repository](https://docs.devolutions.net/powershell-universal/config/repository.md): Explore how PowerShell Universal stores configuration in the repository folder, covering configuration scripts, templates, and file encoding.
- [Running as a Service Account](https://docs.devolutions.net/powershell-universal/config/running-as-a-service-account.md): Configure PowerShell Universal to run under a Windows service account, including required user rights and script run-as permissions.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/powershell-universal/config.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.