> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/evaluations-and-observability/feedback-reporting-access-and-data-export.md).

# Feedback, Reporting Access, and Data Export

Feedback records users’ assessments of responses. Combine it with run details to understand what needs improvement.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FvnpTf6csXv3tGm82OpwD%2FG077.mp4?alt=media&token=7c691632-03b6-4662-8fc0-12daab62568a>" %}

## Before you begin

Permission to view feedback and export the relevant report.

## Key concepts

| Term          | Definition                                                                                                                                          |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Feedback      | A user’s assessment of a response or interaction. Interpret it with the corresponding run and available sample size.                                |
| Run           | One execution of a project. Use its run ID to retrieve that execution’s state, input, output, and errors.                                           |
| Filter        | A condition that narrows the records eligible for an operation. A filter can exclude relevant content before ranking occurs.                        |
| Authorization | The decision whether a caller can perform an operation on a resource. Check roles, scopes, organization context, and sharing when access is denied. |
| Retention     | The period or policy for keeping a category of data. Deleting one resource is not a universal retention rule for all related systems.               |

## Review feedback and export reports

1. Select the reporting period and filters.

![Review the reporting period and metrics before interpreting the results.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/GozcbJnn9Fpcep22SVSm/assets/g077-g077-01-overview.png)

Review the reporting period and metrics before interpreting the results.

2. Open the related run for feedback that needs investigation.
3. Export through the supported control and review the included fields before sharing.

You can connect reported problems to the corresponding execution.

## Behavior and limitations

Feedback is subjective and can be sparse. No feedback is not evidence that every answer was useful. Report access can differ from project execution access. Exports may contain user inputs and outputs; share them only with the intended audience.

## Related resources

[Inspect project analytics](https://docs.stackai.com/guides-and-quickstarts/evaluations-and-observability/inspect-project-analytics.md)

[Evaluation Datasets and Input Mapping](https://docs.stackai.com/technical-reference/evaluations-and-observability/evaluation-datasets-and-input-mapping.md)


---

# 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.stackai.com/technical-reference/evaluations-and-observability/feedback-reporting-access-and-data-export.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.
