# Collect responses

> Give your artifact a form and read the answers back.

Kind: guide · ~2 min · Verified v0.237.0 · Next: [Collections, insights and dashboards](https://pr-2197-stg.superartifacts.app/docs/workspace-data.md)

## Goal

Save visitor answers and read them back through your agent.

## What you'll have

A collecting page, stored responses and an export you can inspect.

## Needs

A connected agent with write permission, the questions to ask and an intended audience. Decide what one row represents before building. An anonymous answer sheet identifies a browser profile, not a verified person; a private window can start again.

## Prompt

**Make an RSVP that collects answers**

```prompt
Using the Event RSVP template, build me an RSVP page for something I am planning — ask me one question first. Publish it, send me the link, and tell me where the answers will appear.
```

## Steps

### One policy

1. Have the agent publish a `policy`: the fields, write shape, read audience, retention and caps the platform enforces. A page without a policy stores no visitor responses.

```mermaid
flowchart TB
  V["Visitor submits"] --> G["Validate or refuse"]
  G --> S["Store accepted response"]
  S --> R["Check read permission"]
  R --> D["Raw or masked result"]
```

### Pick the shape

| A row represents | Policy shape |
| --- | --- |
| One person's editable answers | `perUser: single`, `writes: upsert`, `recordCap.perVisitor: 1`, optional fields |
| One final event | `perUser: many`, `writes: append-only` |
| A person's editable item | `perUser: many`, `writes: upsert` |
| An item everyone edits | `perUser: shared`, `writes: upsert`, a declared `key` |

2. Choose reads: `admin` gives visitors no rows; `own` gives their rows; `contributors` gives others' rows after contributing; `public` gives readable rows to visitors who can open the artifact. Other people's rows are masked. Public text fields are capped at 280 characters.
3. Keep policy fields compatible on updates: names keep their first type. An upsert merges supplied fields; `null` clears an optional field. Whole-row replacement removes omitted values.
4. Test saving from the page. Its data-token request must be relative to the page so collection works inside a project too.

### Read, export, erase

**Read the answers and locate the export**

```prompt
Read the responses to <artifact> with super_data, tell me where its Data tab and export are, and explain how to erase a response if someone asks. Erase nothing until I name the response.
```

Use **Data** to filter, expand or export responses, or `super_data` to read them through your agent. Exports follow the caller's access and masking. Erasure removes stored responses; it does not recall exported copies. Visitors can erase their own data, and Owners can erase a named response.

## Check it worked

Submit a test answer, read it back and inspect the export. Erase only the test response and confirm it no longer reads back.

## If not

Check the policy, token and refused write. Browser storage alone does not send answers to the platform.

## Variations

Declared `image`, `video` and `file` fields collect uploads up to 10, 100 and 25 MiB respectively. Uploaded files are at least contact data. See [limits](https://pr-2197-stg.superartifacts.app/docs/reference/limits.md).

Open **Compliance** as the artifact author or an Editor to inspect declared fields, types, personal-data classification, retention and policy history. Use it to check what the artifact is allowed to collect before accepting real responses.

## Next

[Shared pages](https://pr-2197-stg.superartifacts.app/docs/shared-pages.md) or [workspace data](https://pr-2197-stg.superartifacts.app/docs/workspace-data.md).
