Databases and views

A clear place for the details.

Keep client requests, form responses, and project decisions in typed tables. Use saved views to focus the work and charts to explain the numbers.

Read the guide Start with a prompt

Example project ACORN STUDIO

PROJECT REQUESTS

The next steps, together.

Example project request records
Request	Status	Files
Autumn campaign	New	3
Welcome guide	In progress	1
Brand refresh	Ready	5

One table Different views of the work

Illustrative example · fictional project data

Make the table fit the job

Choose fields for dates, choices, numbers, text, and files. Keep internal tracking fields alongside the information people submit.

Find the next thing to do

Filter and sort saved views for a project, a status, or a deadline. Keep one source of records with different ways to read it.

Turn records into a report

Chart supported fields, export your data, or ask a connected agent to assemble a dated summary with links to the source.

Make it your own

A prompt to get you started.

Connect your AI to Fermium, replace the bracketed details, and bring the source material.

Create a client request table with project, request, owner email, status, and due date. Add views for new requests and items due this week. Keep internal notes out of the intake form.

Read the setup guide

What to know

Views organize records; they don't change who can see them. Your agent writes summaries when you ask, not on a schedule. Charts use single-value fields such as numbers, dates, and choices.

Questions about databases and views

When should I use a database instead of a page?

Use a database for records you need to sort, filter, or update separately, such as project requests, client responses, or purchase decisions. Choose fields for dates, numbers, choices, and files. Use a published page when you want to explain those records in a narrative, such as a status report or a recommendation.

Do saved views change access to the records?

No. A view saves a way to read a table, including its filters, sorting, and visible fields. It does not create a separate permission boundary. Keep the database shared with the people who should see its records, and use a form when someone should submit information without opening the response table.

Can I take the data into another tool?

Export a table as CSV, or download the database as JSON or SQLite. You can also ask a connected agent to read permitted records and create a report. An exported copy stays with its recipient even if you later change access to the original database.