# Collections, insights and dashboards

> Keep editable entries and ask questions across collected data.

Kind: guide · ~2 min · Verified v0.237.0 · Next: [Shared and live pages](https://pr-2197-stg.superartifacts.app/docs/shared-pages.md)

## Goal

Maintain editable records and ask questions across collected responses.

## What you'll have

A Clients collection, entries and an Insights question you can save to a dashboard.

## Needs

A connected agent allowed to define collections and write entries. For Insights, an accessible response source with declared measures: numeric fields and the operations allowed on them. Insights and Dashboards must be enabled in your deployment.

## Prompt

**Create a collection and explore your data**

```prompt
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.
```

## Steps

### Collections and entries

1. Define the Clients fields with `super_data_schema` or **Data → Collections**. A collection describes records you maintain, unlike an artifact policy governing visitor submissions.
2. Add entries through the entry table or `super_entries`. Entries can be draft, published or archived. Authored collections also import CSV or NDJSON files and export CSV; imports validate rows against the saved fields.
3. Classify personal data. Contact data is masked for non-owners; sensitive data is encrypted and cannot be filtered. A `secret` text field holds a credential the agent cannot read; [stored secrets](https://pr-2197-stg.superartifacts.app/docs/secrets.md) explains approved use.
4. Review later schema changes carefully. Field types stay fixed. Defining an existing collection replaces the whole model: include every field you want to keep. Omitted fields are removed.

### Insights

5. Choose a response source, measures and optional grouping in **Insights**, then **Run**. `super_data_query` can query measures too. For non-owners, groups below the privacy floor have values withheld; owners see true totals.

### Dashboards

6. Save the question, then choose **Add to dashboard** on its saved view. Each tile reruns under its viewer's own access. Sharing the layout grants no additional access to its source data, so people can see different results.

## Check it worked

Clients shows the saved fields and entries. Insights returns the expected question result and its saved view becomes a dashboard tile.

## If not

Check source access and declared measures. A withheld value is not zero. If the deployment hides Insights, keep the collection and ask the operator about availability.

## Variations

Publish a page with `policy.collections` to expose permitted collection reads or owner edits. Collections also support image, video, file and reference fields; visitor answers remain governed by their own policy.

## Next

[Three shapes of data](https://pr-2197-stg.superartifacts.app/docs/concepts/data.md) and [limits](https://pr-2197-stg.superartifacts.app/docs/reference/limits.md).
