> 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/survey-builder.md).

# Survey Builder

Every Feedback Survey is built from a list of **questions** — starting with a main question (Rating, Number Pick, or Text for comment-only surveys), a comment question, and an email question, all created automatically when you create the survey. Open the **Survey builder** tab on a survey's settings to add more questions, reorder them, hide the ones you don't need, or edit any of them.

{% hint style="info" %}
The built-in **CSAT** survey uses this exact same screen, but can't have extra questions added — its answers are read and written directly from the Jira request, so extra questions would have no way to be answered. See Built in Feedback Surveys.
{% endhint %}

## Question types

When adding a question, you can choose from:

| Type            | Format        | Notes                                                                                                                                           |
| --------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rating**      | 1–5 stars     | Can carry a calculation strategy and show its own score widget. Rating marks (stars, faces, hearts, or hands) are chosen on the Appearance tab. |
| **Number Pick** | 0–10 scale    | Has an optional **Helper text** shown under the scale. Can carry a calculation strategy and show its own score widget.                          |
| **Text**        | Free text     | Configurable **Placeholder text** and **Max length** (up to 5000 characters). Never has a calculation strategy.                                 |
| **Embed field** | Hidden string | Filled from website `data-myra-fields`. Never shown to respondents. See Embed fields.                                                           |

An **Email** question is always present too, but it's reserved — you can't add another one, only reorder, hide, or edit its text. It's only shown to customers filling out the survey on a **public standalone page or website embed** — it never appears on the JSM portal or request panel.

## Editing a question

Click the edit icon on a question to open its editor:

* **Question text** — the prompt shown to customers (for Embed fields, this is the report column label).
* **Embed key** (Embed field only, create-only) — must match a key in `data-myra-fields` on your website markup.
* **Helper text** (Number Pick only) or **Placeholder text** (Text only).
* **Mandatory question** — toggle to require an answer. **A mandatory question can't also be hidden.** Embed fields cannot be mandatory.
* **Max length** (Text only).
* **Calculation strategy** (Rating/Number Pick only) — Average, Sum, Count, Mode, NPS, or None. Choosing **None** turns off that question's widgets. See Understand Calculation strategies. Embed fields cannot have a calculation strategy or a score widget.
* **Show as portal widget** — only available once a real calculation strategy is set. Turning this on (or its Help Center equivalent, managed from **Display & scoring**) reveals a **Widget display text** field — the caption shown next to that question's own score.

Nothing is saved to the survey until you click **Save changes** at the top of the tab.

## Reordering, hiding, and deleting

Each question card has drag handles and controls to move it up/down, hide/show it, edit it, or delete it.

{% hint style="info" %}
**Hide vs. delete**

* **Hide** is safe and reversible: the question disappears from new submissions and customer-facing forms, but stays in the list and its historical answers remain saved and reportable. **A mandatory question can't be hidden** — make it optional first if you need to hide it. **Embed fields cannot be hidden** — they are already excluded from customer-facing forms.
* **Delete** is permanent: it removes the question and its translated labels (behind a confirmation step), and drops it from future reports. Past answers already collected are retained internally but are no longer shown anywhere.
  {% endhint %}

The main rating/number question, the comment question, and the email question are marked with a **Main** label and can be reordered and hidden like any other question, but — being the built-in backbone of every survey — they can't be deleted.

## What happens when you add a question

When you add a question in Survey Builder:

* It's immediately part of the form everywhere the survey is filled out — request panels, portal forms, public survey pages, and website embeds (unless it's Email, which is public-only — see above). **Embed fields** are the exception: they are filled only from website collection embeds, never rendered to respondents.
* It does **not** automatically get its own score widget. Turn that on separately, per surface (portal / help center / external website), in Display configuration.
* It isn't translatable into other languages yet. Open **Translations** afterward to add its labels there — see Translation Studio.

To brand logo, page background, colors, roundness, and rating symbols, use the Appearance tab.


---

# 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/survey-builder.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.
