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

# Live pages

> Checklists, polls and trackers that keep data shared between everyone who opens them.

A live page is a page that remembers things. Ask your agent for one: "Make a checklist for the offsite that everyone on the team can tick off" or "Make a poll for lunch on Friday".

Polls, checklists and trackers all work this way. Everyone who opens the page sees the same data, and changes show up for everyone as they happen.

## What the page needs

A live page asks for permission to use certain features. You can see and change them in the **Share** panel under **Live data**:

| Setting | What it lets the page do |
| - | - |
| **Database** | Store data that every viewer sees |
| **Viewer identity** | See who is viewing |
| **Viewer's own data** | Lets the page save data for each logged-in viewer, such as their own ticked boxes. |

Your agent switches these on when it builds the page.

## Who can write

Under **Who can change the live data**, pick one:

| Choice | Who can change the data |
| - | - |
| **Everyone who can see it** | Anyone who can open the page |
| **Only editors** | You and the people you made editors. Everyone else can read the data but not change it. |

On a public page, "everyone who can see it" means anyone with the link, logged in or not.

Guests can read live pages but cannot change their data.

Your data stays with the artifact. A new version of the page sees the same data.

## Public live pages

You can make a live page public so that people can vote or add to it without logging in. Know the risks before you do:

* Anyone with the link can change the data, and can overwrite or delete other people's entries. Pick **Only editors** if only you or your agent should change it, for example a dashboard.
* Visitors who are not logged in are not people you can identify. Each browser gets an anonymous id. It is not a person or an account, and anyone can reset theirs by clearing their browser data.
* Public pages are limited to 30 writes a minute for each network address. Everyone in one office or classroom shares that limit.
* Logged-in viewers can make 100 writes a minute.
* A refused or failed save should show a message. Ask your agent to check that the page does this.

> [!WARNING]
>
> Do not put private or sensitive information in a public live page. Anyone with the link can read it.

Before you share a public live page, ask your agent to check it against the public live pages checklist in the runtime API reference, and to test it in two different browsers.

## Reading and editing the data

Ask your agent to read or change the data: "Show me the results of the lunch poll" or "Add three items to the offsite checklist". It uses the same data the page uses.

## For developers

The page code uses `window.openArtifacts`. See the [Runtime API reference](https://docs.open-artifacts.com/technical-details/runtime-api.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.