Use a database when a project needs information that you want to sort, filter, chart, or update over time. Keep it beside the project's files. Its tables and responses follow the same sharing rules as the database document.

Collect information from a client

Open the project folder in Library and choose New → Database & forms, or choose New database under Data. Start with the requests template or an empty database.
Add a table and choose its fields. Field labels appear on forms; types such as date, email, number, and select help keep answers consistent.
Open the database's Forms tab and choose New form. Select the fields to collect and choose who can access the form: Anyone with the link, People with a password, or Restricted to selected people. The form is a separate file, so its Access tab can use the same person, group and folder grants as other files.
Enable Email me when someone completes the form if outgoing email is configured. Every new submission also creates an in-app notification.
Share the form link. Respondents can submit the selected fields without gaining access to your response table.

The generated form has a responsive design. Customize page opens its HTML document; an agent can replace the layout, colors, headings, and other design elements while preserving its submission placeholders. Responses stay behind the database's own access controls, even when the form is public.

Save progress and return later

New forms save answers as the respondent works. The first answer creates a draft row; later answers update that row. Required questions can remain unfinished until the respondent chooses Send response. The page shows when changes have saved and offers a private resume link for another device. Returning in the same browser restores the saved response automatically.

Resume links open only that person's selected form fields, after any password or workspace access checks. Keep them private. They do not open the table or other responses. Completed responses can be revisited but cannot be changed by the respondent. The team can still edit the record in Fermium.

Use the Response column to filter drafts and completed responses or chart completion status. Drafts save quietly by default. In the form settings, choose Also notify when a draft starts if you want an initial notice as well as the completion notice. Save partial responses controls autosave for that form.

Keep the page open while it reports unsaved changes or a connection failure. Only answers confirmed as saved survive closing or reloading the page. If another tab changes the same response, review the conflict before continuing.

Work with responses

Use Long text for detailed written answers, Multiple select for several choices, Date and time for a timezone-aware timestamp, and Structured JSON for objects and lists. Each response supports up to 1 MiB; long-text fields allow 262,144 characters each, within that response limit. A text column can be widened to long text in the table settings without recreating its records.

JSON and date/time drafts can hold unfinished input; completion validates them. Multiple-select charts count each selected option, so one response can appear in several groups. Exports preserve structured values as JSON text in CSV and SQLite.

Collect files and review them

Add a Files & screenshots field to accept one or more uploads, drag and drop, or pasted screenshots. Choose a destination folder, file count and size limits, and optional accepted extensions. Any file type can be collected; previews depend on the format. Files live in the database's root, in the selected folder or the database folder.

Add a File review field to review existing Fermium files, files supplied in a Files field, or both. Select the original files in the table settings. The selected versions become visible to people who can open a form with this field, including guests. You need edit access to a source to share it this way.

Use pins, rectangles, arrows, or drawing to mark images and PDF pages. Video comments keep their playback timestamp; supported audio also accepts timestamped comments. Other formats offer downloads and general comments. Select a comment to return to its source, page, or moment. Choose Add comment before submitting.

A form containing only these fields is a standalone file request or review page. Combine them with normal questions when you need a fuller response. Media forms require Save partial responses. Each guest sees their own feedback and uploads; the team can open response records to review, reply, or resolve comments. Completed responses are read-only for the guest. This is not yet a shared conversation across different guests, and replies do not currently carry separate author identities.

Keep the page open while files upload. Failed uploads offer Retry and Discard; submission waits for uploads to finish. Saved responses retain their files. Abandoned uploads expire after seven days. Removing a file reference does not delete the stored document. Live website capture is planned through a browser extension first, then the desktop app.

Double-click a cell to edit, then press Enter to save. Open a numbered row for all its fields, including on a phone. Concurrent edits produce a conflict instead of silently overwriting someone else's work.

Use search, column sorting, filters, and hidden fields to find the right rows. Save view keeps those settings for the team. Charts groups and aggregates all matching rows, including those beyond the current page. Activity shows changes and notification outcomes without copying answers into logs.

Export a table as CSV or the database as JSON or SQLite. The SQLite download contains only that project's data and schema. A downloaded copy cannot be revoked when sharing changes later.

Connect the next step

Connections can send selected answer fields to n8n, Zapier, or a custom webhook. Choose an event such as a form submission, send a synthetic test, and inspect delivery status. The existing webhook plan and administrator access requirements apply. Use Edit URL to replace an n8n test URL with the published workflow's production URL.

Your agent can also check for changes through MCP. A quick status call returns a revision; it fetches records only when that revision changes. The agent needs an active run or an external scheduler to keep checking.

Prompts to try

Browse the workflow and prompt library for client questionnaires, onboarding, requests, events, research, and automation examples.

“Create a production questionnaire in this client folder. Keep the response database private to our team. Style the form to match the proposal, and email me when the client responds.”
“Show the new requests, grouped by status. Create a chart of estimated cost and save a view of requests waiting on the client.”
“Connect submissions to this n8n workflow, sending only client, email, and request. Use a synthetic test and show me whether it was accepted.”
“Read changes since my saved cursor. Summarize new responses, link to their records, and save the new cursor after processing them.”

This release supports small project databases and forms. Relationships, calculated fields, editing completed responses as a respondent, and general browser app queries are planned extensions. See the developer reference for API details, access behavior, and current limits.

Databases and forms