Collections, insights and dashboards

Keep editable entries and ask questions across collected data.

guide~2 minVerified v0.71.0

The collection schema builder with text, email, choice and date fields. — A collection describes entries a person maintains.

You will have a Clients collection, and views of data your artifacts collected.

Create a collection and explore your data

Create a Super Artifacts collection called Clients with name (text), email (email, contact data), plan (choice: Pilot, Studio, Enterprise), and renewal (date). Add the clients I give you as entries. Show me the collection link. Then help me run a grouped query in Insights on a tracker I have, and check whether Dashboards can display the saved layout. If it cannot, tell me and keep the collection and query result.

Collections and entries

Collections hold records you maintain: clients, a catalogue or a reading list. The schema gives each field a type, such as text, email, choice or date. Personal-data classes describe how a value is protected. Saved field types stay fixed once entries exist.

The Clients collection's entries table. — Entries are the records inside the collection.

The entry table is where the records live; an entry can be a draft or published. Your agent can work with them through super_entries. Data collected from visitors follows the artifact's policy instead of becoming freely editable schema.

Insights

Insights reads data your artifacts collected. Sources declare measures: numbers that can be combined. A grouped question can show a total by day or by a field. Small groups have their values withheld while their counts remain.

Dashboards

A dashboard lays saved Insights questions side by side; every tile runs with the viewer's own access. No picture here: the dashboards list showed nothing when this guide was checked, so it is not claimed as working.

Check it worked

Clients shows the saved fields and entries. Insights shows an answer to the chosen question.

Next: Limits.