> 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/apps/themes/colors.md).

# Colors

Set component colors in PowerShell Universal apps using hex values, RGB strings, or named colors through the Color parameter on supported cmdlets.

Many components accept a color parameter. Some color parameters allow you to select from a preset style like success and error. Other color parameters accept a `DashboardColor` object that can define a specific color using a name, hex value or RGB value.

Below is an example of each type of configuration. A list of [known colors can be found here](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.knowncolor?view=net-9.0).

```powershell
# Hex color 
New-UDIcon -Icon User -Color '#2596be'

# RGB values
New-UDIcon -Icon User -Color 'rgb(37, 150, 190)'

# Anything Color.FromName knows
New-UDIcon -Icon User -Color 'gray'
```


---

# 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.devolutions.net/powershell-universal/apps/themes/colors.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.