Records & Lists
Records & Lists owns live data and the collections people use to work with it. Start here to inspect values, gather Records, or save a view.
Boundary
Records & Lists stores values under the kinds that Company Schema declares. A List gathers Records without defining their shape. A View changes how you read them without changing their values. Data Pipelines owns imports and their lineage. Membership in a List does not replace that origin or grant access to a Record.
Services
Records & Lists separates a Record's values from membership and presentation. Choose the service by the change you want to make, so a saved display does not stand in for a shared work target.
| Reader decision | Start with |
|---|---|
| Inspect a Record or compare its changes | Records and history explains identity and past values. |
| Gather Records into a durable target | Lists and membership explains kinds, targets, and ordering. |
| Save a presentation or return to it | Views and presentation explains saved views and pins. |
Start here
Records & Lists opens Records at /records and All Lists at /lists in the Console. Import and target records connects an imported Record to its origin and a List. For a known Record, entities.get reads its current values with access rules applied. Use the returned Record to check a write before acting on it again.
Next steps
- Records and history helps an operator distinguish current values from a past state.
- Create a list walks an operator through the Console creation dialog.
- API reference gives builders exact Record and List call contracts. API supplies the HTTP setup.