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

# Collection configuration

When opening a Feedback Survey, navigate to the **Collection** tab within your settings menu. This is your command center for defining exactly how feedback is collected from your customers.

* **Enable Collection**
  * This is the master switch that allows customers to submit feedback.
  * New surveys start paused — enable collection to activate your survey and unlock sharing options.
  * For **Project** and **Public** scopes, enabling collection also generates a standalone **Public survey link** and embed markup on the **Sharing & embed** tab.

![Enable collection](https://cdn.sandbox.getmyra.app/docs/collection/collection-tab.glossy.png)

{% hint style="info" %}
Want to turn the comment question on or off, make it mandatory, or change its text? That's no longer a toggle on this tab — open the **Survey builder** tab and edit (or hide) the comment question directly. See Survey Builder.
{% endhint %}

* **Collection Rules**
  * Define when and for whom feedback should be requested — for example, only on resolved requests, after a cooling-off period, on specific days, or within a date range.
  * Collection rules are **restrictive**. With no rules, or with all rules disabled, collection remains allowed.
  * When multiple enabled rules exist, they all must pass for the survey to appear.
  * These rules also affect standalone and embedded survey collection wherever that survey is available.
  * Request-scoped surveys can wait until **this** request has been resolved for a configured time — see Understand Collection rules.

**Sharing options (Project & Public scopes)**

When collection is enabled for a **Project** or **Public** survey, open the **Sharing & embed** tab to access:

* **Public survey link** — a standalone URL customers can open without Jira access.
* **Website embed prerequisite** — the shared `widget-embed.js` script to install once per website.
* **Collection embed markup**
  * **Popup button** — a `data-myra-survey` snippet that opens the feedback form in a popup.
  * **Inline form** — a `data-myra-survey-inline` container that renders the form directly on the page.
* **Public score display** markup — a `data-myra-widget` div snippet (requires **Public score display** to be enabled on the Display & scoring tab).
* **Question widget embed codes** — once you've enabled a Portal or Help center widget for one or more questions in **Display & scoring → Widgets**, their individual `data-myra-widget` snippets appear here too, below the survey-level codes.

![Public link and embed](https://cdn.sandbox.getmyra.app/docs/sharing/public-link-and-embed.glossy.png)

{% hint style="info" %}
Standalone survey links and collection embeds are **not available** for **Request** scope surveys, because reporter and request context are not available outside the portal.
{% endhint %}

**Portal survey carousel**

On the JSM customer portal and request panels, when multiple **Request**- or **Project**-scoped surveys are collectible at the same time, Myra presents them in a **multi-step carousel** instead of stacking forms on the page.

* Customers see one survey at a time with progress indicators.
* They can move **Back**, **Next**, or **Skip** individual surveys, and **Finish** when done.
* Each step respects that survey's collection rules and label configuration.

If only one survey is available, the carousel is not shown — customers see a single form instead.

**Survey order**

When multiple surveys can appear in the same panel, you can control which survey customers see first.

* On the **Settings** tab, click **Survey order** (available when you have two or more collectible **Request**- or **Project**-scoped surveys in the same panel).
* Drag surveys to reorder them, or use the up/down arrow controls.
* **Request panel** and **Project panel** have independent order lists.
* Surveys with collection disabled appear at the bottom labeled **Not collecting** and cannot be reordered until collection is enabled.
* Click **Save changes** to persist the order for your project.

![Survey order](https://cdn.sandbox.getmyra.app/docs/collection/survey-order.glossy.png)

{% hint style="info" %}
Survey order only controls **sequence** in the carousel. Whether a survey appears at all is still determined by that survey's **Enable Collection** toggle and **Collection Rules**.
{% 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/collection-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.
