App tables

Create structured tables, extract document values, and preserve evidence for reviewed results.

App tables hold structured data within an App. They can be created manually, populated by an App workflow, proposed by the Assistant, or generated from selected documents. They are separate from the tables you administer through a database connection and from read-only table-shaped records in Data.

Two ways to start

Create a table from the App's Tables section when you know the name and column types you need. Add or populate rows through the App's supported editing and workflow controls.

For document-backed data, select the source files and generate a table draft. Strive captures the sources, proposes fields and values, and presents a review before saving. Some Apps prepare the first draft after upload, but explicit acceptance still creates the saved table.

Work with saved tables

Open a table from the Tables list to read it in a tab. Opening the same table again focuses the existing tab. Closing a tab does not delete the table, and reopening loads its saved rows again. The tab strip is temporary browsing state; the table and its accepted data persist.

Editable tables support adding rows, editing cells, deleting rows, and managing the table name. Read-only and shared experiences can expose fewer actions. The App's capabilities and your access determine which controls appear.

Review meaning as well as values

A column's name, type, and definition describe what its values mean. Removing or reordering proposed columns is different from changing a field's definition. A meaning or type change requires fresh extraction so old values are not relabeled as new facts.

Saved extraction cells can link to captured evidence. Manual edits must not inherit that old evidence as proof of a new value. Use evidence and origin before relying on a table for an important decision.

Continue with manual creation, document extraction, or editing.