---
title: The research export
description: Download a study's documented ZIP, read its consent marks, cite what learners saw, and delete a learner's data.
updated: 2026-10-29
---

> All VIABLE docs, for people and their agents: https://developers.viablelab.org/llms.txt

# The research export

Get your data out as one documented ZIP, ready to analyze and cite. A study's **Export** tab opens [Research → Export](/dashboard/research/export) with the study chosen.

::: steps
1. **Choose whose data.** Pick a study, a course, or where (courses, chat pages, your apps on the API). Turn off **Only people included in the study** to get everyone, each record marked.
2. **Choose when and which agents.** Choosing agents leaves out activities without AI.
3. **Choose what goes in.** Turn on **What was written**, **IDs from your systems**, **Recordings** or **Mask condition names** as needed.
4. **Download.** **What's in the ZIP** lists the files this selection fills. Then select **Download ZIP**.
:::

A study's export never holds app data. An export holds up to 250,000 turns, and every export is listed under **Research activity** on [Research → Overview](/dashboard/research).

## What's in the ZIP

- **People and conversations:** `learners.csv`; `turns.csv`, every message and reply with agent version, sources and rating; `agents.csv`.
- **Work and measures:** `sessions.csv`, `attempts.csv` (pyBKT format), `outcomes.csv`, `writing.csv`, `responses.csv`, `activity_progress.csv` and more.
- **The study:** `enrollments.csv` (decisions), `assignments.csv`, `flow.csv` (CONSORT counts), `study_events.csv` and `study_documents.csv`.
- **Coding:** `coding_labels.csv`, `coding_final.csv` and `codebooks.json`.
- **The dictionary:** `data_dictionary.csv` defines every column and its sources. `manifest.json` records your choices, the protocol and checksums.

Names, typed IDs and personal codes never leave the dashboard.

## Consent marks

Records from a study carry `study`, `condition` and `participation`. The `participation` mark is `included`, `opted_out`, `declined`, `withdrawn`, `awaiting_permission` or `not_in_study`. Inclusion is decided at export, never by deleting records.

## Masked conditions and recordings

Masked conditions appear as A, B and so on, without their names, rules or agents' names. The study's **Data** tab sets the default.

Recordings exist only when **Keep recordings of what people say** is on in **Data**. Once the study opens, you can turn it off but not on. `recordings/` holds them only for people whose data counts. `turns.csv` and `responses.csv` name each file.

## Citing what learners saw

- **Activities:** records carry `activity_version`, and `manifest.json` lists each version's settings SHA-256.
- **Agents:** turns carry `agent_version`, and `agents.csv` gives each workflow's SHA-256. For a comparative study, the manifest gives pinned versions and the protocol version.
- **Forms:** decisions carry their form version, and `study_documents.csv` gives each PDF's SHA-256.
- **Coding:** `codebooks.json` gives codebook versions, seeds, and each model coder's settings and prompt.

## Deleting a learner's data

::: steps
1. **Find the person.** Open them in [Teach → Learners](/dashboard/learners), or under **Chat page visitors**.
2. **Delete.** Select **Delete data…**, then **Delete their data**.
:::

> [!WARNING]
> This can't be undone. Their messages, answers, drafts, scores, coding labels, recordings and what agents remembered are deleted, and so is a learner's name. Their study decisions and code stay, as review boards require, and `learners.csv` marks `data_deleted_at`. Owners and editors delete.

::: cards
- [Coding conversations](/docs/research/coding): code a sample before you export.
- [Consent and taking part](/docs/research/consent): what each consent mark means.
:::