# Shared and live pages

> A board, a survey, a quiz or a plan: pick the shape, then copy its prompt.

Kind: guide · ~2 min · Verified v0.237.0 · Next: [Webhooks](https://pr-2197-stg.superartifacts.app/docs/webhooks.md)

## Goal

Choose the data shape for a page several people use.

## What you'll have

A board, survey, quiz or plan with the intended ownership and live updates.

## Needs

A connected agent with write permission, the people who should open the page and a row model. Shared-row editing is different from editing the document's source. Check your workspace's available live rooms.

## Prompt

Choose the matching prompt below after deciding who may open the page.

## Steps

| You want | A row represents | Who changes it |
| --- | --- | --- |
| Board | One keyed note | Anyone admitted to the shared document |
| Survey | One visitor's answers | That visitor |
| Quiz | One final answer per question | No replacement in an append-only log |
| Plan or roster | One keyed item | Anyone admitted to the shared document |

### A board

**Build a shared board.** Your agent builds shared notes with live updates.

```prompt
Build a shared board in Super Artifacts where the people I invite add notes and move anyone’s note, and every open screen updates without a reload. Ask who it is for and what a note holds. Declare perUser shared with key note_id (a required text, max 120, the page makes for each new note), writes upsert, read public (on a private artifact that is only the people who can open it), fields for the text (max 280), x, y and colour, and no personal data. Show who wrote each note from the row’s author label, not from a name field the page fills in. Subscribe to the live room for new, moved and deleted notes and ping every 30 seconds; read super_help live first. Publish with super_publish, keep it private, invite the people I name with super_share and return the link. Test with two browsers before you hand it over.
```

### A survey

**Build a survey people can come back to.** Your agent builds an answer sheet with one optional field per question.

```prompt
Build a survey in Super Artifacts whose answers people can come back and change. Ask for the questions and who answers. Declare an answer sheet: perUser single, writes upsert, read own, recordCap perVisitor 1, one optional field per question. Long answers are text with max 2000, a rating is an integer from 1 to 5, and a pick-all-that-apply question is one boolean field per option. On load, read this visitor’s row with scope own and fill the form; save each answer as it changes, and send null to clear one. Publish with super_publish, keep it private with super_artifact_set, arrange only the audience I choose and return the link. After I answer twice, read it back with super_data and show me one row with my latest answers.
```

A pick-all-that-apply question uses one boolean per option. Sending `null` clears an optional answer. On an anonymous page, one visitor means one browser profile, not verified identity.

### A quiz

**Build a scored live quiz.** Your agent builds a quiz with the answer key in an owner-only stream.

```prompt
Build a scored live quiz in Super Artifacts by hand, not from a template, so the answer key never reaches a player’s phone. Ask for the questions, the answers and who plays. Keep the key in a stream only the owner reads and writes; put each question on a stream the owner writes and everyone reads; take answers on a stream players read as their own, with uniqueBy question_no so each player answers each question once, writeAt question so answers land only while a question is open, and revealAt results. Add a public tally. The host screen is my own signed-in page or a named Editor’s; move the phase from it or with super_artifact_set. Score from the server’s at times, never the phone’s clock. Read super_help live first, ping every 30 seconds, publish privately and test with two phones.
```

The [live quiz recipe](https://pr-2197-stg.superartifacts.app/docs/recipes/live-room.md) explains when the practice template is suitable. Its answer key travels inside the page; keep it off player devices when the score matters.

### A plan

**Build a shared plan.** Your agent builds one shared row per item.

```prompt
Build a shared plan in Super Artifacts that anyone I share it with can edit, one row per item, with the newest edit winning. Ask for the items and the columns. Declare perUser shared with key set to the item field (a choice or a short text), writes upsert, read public (on a private artifact that is only the people who can open it), and recordCap perArtifact as the number of items. Every save carries the item’s key and only the fields it changed; an empty field sent as null is cleared. Show updatedAt as the last edit, and subscribe to the live room so other people’s edits appear without a reload. Public text fields stay at 280 characters or less. Publish privately with super_publish, arrange the audience I choose and return the link.
```

Shared saves merge changed fields. If people change the same field, the last write wins without a conflict notification. Each item records `updatedAt`.

### What other people see

Other writers' rows are masked. On a private artifact, signed-in named readers can see another named writer's display name as author. Do not rely on readable token claims as a supported visitor-identity interface.

### Live updates

A [live room](https://pr-2197-stg.superartifacts.app/docs/concepts/live-rooms.md) carries data updates. Document-source co-editing uses a separate room and capacity pool; it is not a shared-row policy.

## Check it worked

Test in two browsers: submit, edit and reload. Check who can read each row and whether open screens update.

## If not

Check access, the policy and room capacity. A refused live connection does not itself prevent valid data writes.

## Variations

**Which artifacts hold a live room**

```prompt
Which of my Super Artifacts are holding a live room right now? Call super_whoami and read liveRooms: tell me how many rooms my workspace may hold at once and, for each one held, the artifact and since when. If I want another artifact live and every room is taken, suggest which to turn off with super_artifact_set live false, and change nothing until I say which; afterwards tell me how many open pages it disconnected.
```

## Next

[Live rooms](https://pr-2197-stg.superartifacts.app/docs/concepts/live-rooms.md).
