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

# Understand Survey scopes

## Understand Survey scopes

### Survey scopes

When creating a new Feedback Survey you can choose from the following **scopes**:

* Request
* Project
* Public

**Request scope** lets you tie collected feedback to each request. Feedback can only be collected within the request context, but you can display the feedback score in the JSM portal or on your own website.

**Project scope** lets you collect feedback on the portal page and display the feedback score in the JSM portal or on your own website.

Request and Project scope Feedback Surveys will always be linked to the current project that the Feedback Survey was created in.

**Public scope** lets you create Feedback Surveys you can embed on external websites or share via a standalone link. Public scoped surveys can be created from a given Project's settings (automatically linked to that project) or from the global app (where you manually link the survey to a project).

Survey Scopes define the context in which feedback is collected and where the resulting data is linked within Myra.

**Request Scope**

* **Context:** Tied specifically to individual requests.
* **Collection:** Feedback is gathered within the context of a specific request.
* **Portal carousel:** When multiple request-scoped surveys are collectible on the same ticket, customers see them in a step-by-step carousel with Back, Next, Skip, and Finish controls.
* **Visibility:** Scores can be displayed within the Customer Portal or embedded on your own website.
* **Sharing:** Standalone links and website embed markup are **not** available — reporter and request context are required.

**Project Scope**

* **Context:** Tied to the broader Project level.
* **Collection:** Feedback is collected on the JSM portal page (and via standalone link or website embed).
* **Portal carousel:** When multiple project-scoped surveys are collectible at once, customers see them in a step-by-step carousel with Back, Next, Skip, and Finish controls. Use **Survey order** in settings to control which survey appears first.
* **Visibility:** Scores can be displayed within the JSM portal, Help Center, or on external websites.

{% hint style="info" %}
Both Request and Project scopes are strictly linked to the specific project in which the survey was originally created.
{% endhint %}

**Public Scope**

* **Context:** Independent of a specific portal location.
* **Collection:** Collect feedback anywhere via website embed (`data-myra-survey`) or a standalone public link.
* **Configuration:** If created within **Project Settings**, it is automatically linked to that project. If created via the **Global App**, you must manually select the project you wish to link the data to.
* **Embed model:** Requires the shared `widget-embed.js` script once per website, plus per-survey markup from the **Sharing & embed** 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/understand-survey-scopes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.