> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/style-branding/style-editor/style.md).

# Style

## 🎨 What is the style tab ?

The style tab allows you to set general properties on your style and to [add a header logo](/form-management/style-branding/style-editor/style/header-logo-image.md) that will be displayed on top of your survey. 

## 🔅 Style properties

* **`Style name`** Display name of the style.
* **`Built in`** a built in style is a style that is accessible by all ngSurvey's users but that is only editable by administrators.
* **`Shared`** let you share your style with other users. At the moment all users will have access to your style if you share it.
* **`Dark`** indicates if you style should support dark mode. ngSurvey will switch its [form designer](/form-management/form-designer.md) to a dark mode based designer if the survey has a dark mode enabled style assigned to it.

## 🌈 Color Wizard

Using the color wizard you can select a primary color and secondary color that will be used to generated a set of matching colors for your survey [theme](/form-management/style-branding/style-editor/theme.md). 

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBcKMmayrpHOsZik4eI%2F-MBcKy4IHya-AHEhRBqP%2Fimage.png?alt=media\&token=4efa8909-8750-4ff9-9716-63bc24a8c22a)

The **primary color** is the color that will be displayed the most frequently across your survey components, the **secondary color** accents actionable survey components like for example [radio buttons or checkboxes](/form-management/form-designer/answers/answer-types/selection-answers.md). 


---

# 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.ngsurvey.com/form-management/style-branding/style-editor/style.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.