> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insito.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Responses

> Where to browse individual survey responses and export them to CSV.

There are three places to read responses in the dashboard. There is currently
no single project-wide "Responses" page — responses live on the project
**Overview**, the **survey detail** page, and the **builder Responses tab**.

## Overview → Recent responses

The project Overview has a **Recent responses** table showing the latest
responses across the project, flattened one row per answer. It's a quick pulse
check; it doesn't have filters or export.

## Survey detail → Responses

Open a survey from the survey list. Its **Responses** tab shows that survey's
responses as cards with **Previous / Next** pagination. Each card lists the
answers for one response, including a **Partial** badge for autosaved,
in-progress sessions.

## Builder → Responses tab

Inside the survey builder, each saved survey has a **Responses** tab next to
Questions, Logic, Trigger, Audience, and Schedule. It's a focused, full-width
view of just that survey's responses:

* **Table with infinite scroll** — responses load in pages as you scroll,
  newest first. Columns are `Submitted`, `Status`, `Platform`, then one column
  per question (in builder order). Questions a respondent skipped or never
  reached (branching) show an em dash (`—`).
* **Detail panel** — click a row to see the full, untruncated answers; step
  through with the `↑` / `↓` keys.
* **Partial responses** — included inline with a **Partial** badge.
* **Export CSV** — the toolbar's **Export CSV** downloads every response for the
  survey: one header row built from your question text, one row per response,
  multi-select answers joined with `; `, and empty cells for skipped questions.
  This export is **available on all plans** and is not capped.

## Partial responses

When **Autosave progress** is enabled on a survey, the SDK saves in-progress
answers as the respondent moves through questions. These appear with a
**Partial** badge until the user submits. Completing the session upgrades the
same row to **Completed** — you won't get duplicate entries for one respondent.

## Reading responses via the API

To pull responses programmatically (for a warehouse or custom tooling):

* `GET /v1/dashboard/projects/:projectId/responses` — offset-paginated, filter
  by `surveyId`, `platform`, `from`, `to`.
* `GET /v1/dashboard/surveys/:id/responses` — cursor-paginated for one survey.
* `GET /v1/dashboard/surveys/:id/responses/export` — CSV stream.

See [Dashboard endpoints](/api/dashboard-endpoints#responses).

## Privacy

* The dashboard only displays whatever your `identify()` payload contains, so
  avoid sending raw PII in `metadata` / `properties`.
* Free-text answers are stored as-is; scrub anything sensitive before
  submission.