> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/myra-master-your-ratings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/appearance.md).

# Appearance

Brand survey forms and widgets with a logo, page background, theme color, roundness, and rating symbols.

Open a survey's **Appearance** tab to brand the customer-facing form and widgets. Changes save as you pick them, and the live preview on the right updates immediately.

Appearance applies to:

* Standalone public survey pages
* Website collection embeds (popup and inline)
* Help Center widgets
* Portal and website score widgets (roundness and rating symbols; score widgets keep a **neutral** background so the score stays readable)

Jira admin screens (settings, reports, issue panel) stay on Atlassian styling.

![Survey live preview](https://cdn.sandbox.getmyra.app/docs/settings/survey-preview.glossy.png)

## Survey logo

Upload a logo shown in the corner of the survey form on standalone pages, website embeds, and Help Center forms.

* Formats: **PNG**, **JPEG**, **WebP**, or **SVG**
* Maximum size: **512 KB**
* Remove the logo anytime from the same control; the live preview updates as soon as the upload finishes

{% hint style="info" %}
Score widgets do not show the survey logo — only the form customers fill in.
{% endhint %}

## Survey background

Upload a background image shown **behind the standalone public survey page** (the full-page survey opened from a public link).

* Formats: **PNG**, **JPEG**, **WebP**, or **SVG**
* Maximum size: **2 MB**
* Website embeds, Help Center, and score widgets keep their normal surfaces — only the standalone page uses this background

The live preview applies the background so you can check contrast with your theme color before sharing the link.

## Theme color

Choose a recommended palette, or pick a custom accent with the color picker / hex field.

Recommended palettes: **Myra Blue**, **Ocean**, **Teal**, **Forest**, **Sunset**, **Berry**, **Violet**, and **Slate**.

Hover states, page tint, and button text are derived from the accent so the form stays readable. Prefer a reasonably dark, saturated brand color — pale yellows and pastels often fail on buttons and selected ratings.

{% hint style="info" %}
Score widgets keep a **neutral surface**. Theme color still drives rounding and rating symbols on those widgets, but it does not recolor the widget background.
{% endhint %}

## Roundness

Choose how rounded the standalone survey, embeddable widget, and Help Center should feel:

| Style       | Effect                                          |
| ----------- | ----------------------------------------------- |
| **None**    | Sharp corners                                   |
| **Rounded** | Soft rectangles (default)                       |
| **Pill**    | Fully rounded buttons; cards stay a step larger |
| **Custom**  | Set a corner radius from 0–24 px                |

Cards stay a little rounder than buttons so the corners nest.

## Rating symbols

For surveys that include a 1–5 **Rating** question, pick the marks customers tap:

| Symbol     | Scale                           |
| ---------- | ------------------------------- |
| **Stars**  | Classic 1–5 star fill (default) |
| **Faces**  | Angry → delighted               |
| **Hearts** | Broken heart → in love          |
| **Hands**  | Thumbs down → celebration       |

This only changes 1–5 rating questions. **Number Pick** (0–10) scales are unchanged.

The same symbol is used on the standalone survey, embeddable widgets, Help Center, and reports.

![Star rating widget](https://cdn.sandbox.getmyra.app/public-frontend/via-storyboard/widgets/star-rating.glossy.png)

See also Display configuration for score widgets and measurement range, and Survey Builder for question text and calculation strategy.


---

# 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.meta-inf.hu/myra-master-your-ratings/use-myra/appearance.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.
