Tables, datasets, and databases

Choose between a saved snapshot, shared records, and connected data.

A database-like Page can mean several things. Tell the agent whether you need a report over saved data, a shared tracker people can update, or an interface to an existing resource.

Need	Use
A reproducible report from CSV or JSON	Saved dataset and table/chart views
An editable task or decision tracker	Shared work records
Current channel, resource, or agent information	Supported live bindings
Actions on an existing integration or database	An HTML Page using permitted resource tools

A display table is not automatically a spreadsheet, and a saved dataset is not an arbitrary SQL database.

Tables

Supported tables can include sorting, search, column filters, grouping, totals, and export when the author enables them. They can appear beside charts using the same data.

Create a searchable customer research table from these notes, with organization, topic, evidence, and follow-up columns. Keep unknown fields blank and include source references.

Sorting or filtering changes the view. It does not edit the saved source rows.

Saved datasets

Saved datasets retain CSV or JSON independently of an agent’s sandbox. CSV cells remain text; JSON datasets use flat records with scalar values.

Where available, Saved datasets lets you publish a new dataset or a new version of an existing one. Each Page revision binds an exact dataset version.

If you publish version 2, Pages bound to version 1 keep using version 1. Ask the author to update the Page’s binding deliberately.

Save this CSV as a dataset and create a report pinned to that version. Include its version and reporting date in the Page.

A dataset version supports up to 10,000 rows, 100 columns, and 2 MiB. Large sources may need summarization or a more focused extract.

Shared records

Use native shared work components for editable to-dos, decisions, risks, assumptions, milestones, updates, and polls. Their changes are saved separately from document revisions.

Ask for a task tracker when people should check off items or edit task details. Do not assume every custom table has shared persistence.

Live and connected data

Supported read-only bindings can show bounded channel root messages, workspace resource metadata, and agent status. Access is checked when data is read. Historical Page views disconnect live bindings while retaining saved dataset views.

Agent-authored HTML Pages can also use supported resource tools. These may read or change connected resources, depending on the tool and both the viewer’s and original author’s permissions.

For an external database, first establish a supported connection and specify the intended operation. The Page does not gain unrestricted database access simply because someone can open it.

Updating a report

Ask for a new dataset version, update the Page’s binding, and review the resulting chart or table. Retain the old version when you need a reproducible baseline.

See Interactive Pages for connected actions and Evidence and sources for comparisons between revisions.