> 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/display-configuration.md).

# Display configuration

Ensure your public-facing metrics align perfectly with your brand. You can customize exactly how and where your feedback scores are showcased by navigating to the **Display & scoring** tab of your survey settings.

To brand the survey form itself (logo, page background, color, roundness, rating symbols), use the **Appearance** tab instead — see Appearance.

![Display and scoring](https://cdn.sandbox.getmyra.app/docs/display/display-and-scoring.glossy.png)

* **Measurement Range**
  * Define a time window (in days) for your score calculation. This guarantees your widget reflects your *current* service quality rather than an all-time average.
* **Public Score Display**
  * Toggle this **On** to turn your score into a trust signal on external websites. Enabling it allows the score widget markup (copied from the **Sharing & embed** tab) to render live data.
  * You can leave the `<div data-myra-widget="…">` snippet in your HTML even when this toggle is off — the widget area will simply appear empty until you re-enable it.

{% hint style="info" %}
**Display text is now set per question.** There's no single "Display Text" field for the whole survey anymore. Each question that can show a score widget has its own caption, called **Widget display text** — set it when you add or edit the question in **Survey builder**, or fine-tune it per language in **Translations**.
{% endhint %}

### Widgets

Below the toggles above, the **Widgets** section lists every question in your survey that has a usable calculation strategy — your main rating/number question, plus any extra Rating or Number Pick questions you've added in Survey Builder. Each one gets two independent toggles:

| Toggle          | Effect                                                                                          |
| --------------- | ----------------------------------------------------------------------------------------------- |
| **Portal**      | Shows that question's own score widget on the JSM customer portal, alongside the overall score. |
| **Help center** | Shows that question's own score widget on the JSM Help Center.                                  |

* Toggling either switch saves immediately — there's no separate "Save" step for this section.
* A question only appears here once it has a real calculation strategy (Average, Sum, Mode, NPS, or Count). Questions set to **None**, and all **Text**/**Email**/**Embed field** questions, never show a score, so they don't get a widget.
* Once a question has Portal or Help center enabled, its caption is shown as "Shown as: …". Edit that caption from the question's editor in **Survey builder**, or override it per language in **Translations**.
* After you enable a widget, its website embed snippet also appears on **Sharing & embed** (requires **Public score display**).

![Widget preview](https://cdn.sandbox.getmyra.app/docs/settings/widget-preview.glossy.png)

{% hint style="info" %}
Score widgets keep a **neutral background**. Theme color, roundness, and rating symbols from the Appearance tab still apply to the marks and corners.
{% endhint %}

{% hint style="warning" %}
**Content Security Policy (CSP) Requirements**

External score widgets require the shared Myra embed script (`widget-embed.js`) in your page `<head>`. If your website uses CSP, copy the directives from the **Sharing & embed** tab.

For score display embeds, you typically need:

`Content-Security-Policy: script-src 'self' https://<your-forge-app>.hello.atlassian.net; style-src 'self' https://<your-forge-app>.hello.atlassian.net;`

For collection popups and inline forms (`data-myra-survey` / `data-myra-survey-inline`), you also need `connect-src` and `'unsafe-inline'` in `style-src`. The app shows the exact policy for your site.
{% endhint %}


---

# 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/display-configuration.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.
