Forms and submissions
Teams collect leads or table rows through public forms, managing fields and submissions together.
Teams collect leads or table rows through public forms, managing fields and submissions together.
Settings
Options, screen paths and defaults.
Browse this area
Marketing — modules and detailed settings
Where to find it
Web: open Marketing. Desktop: Business → Marketing, using the same record paths. Disabled modules or missing read permission remove the navigation entry.
| Screen / tab | Web path | Usage | Desktop |
|---|---|---|---|
| Forms | /forms | List, view or tab | Native screen |
| Record details | /forms/[id] | Record or editor | Native screen |
Start working
Step 1
Create a lead/table form.
Step 2
Set order, required rules, validation and mapping.
Step 3
Review preview with demo answers.
Step 4
Open and share the form.
Step 5
Export submissions; retry/discard failures.
Settings
Option-by-option configuration and screen paths: Settings guide.
There is no separate settings route; the guide distinguishes record options from declared defaults.
Permissions and limits
Before you start
Closed forms show a closed message at the same link. Table Form views are a separate sharing surface.
Role capabilities: Read (read), Write (write), Manage (manage), Export (export), Own records only (own_records_only), Comment (comment).
Own-record restrictions apply equally to lists, records and Era. Record state or missing data can refuse an otherwise permitted action.
Ask Era
Prepare an application form with name, email and service preference.
Select relevant records for Era context. Era respects modules/roles; external or confirmation-sensitive work can stop for approval. Use era tools in the terminal to inspect currently available tools.
Automation and events
These declared events are available to module-event triggers. Subscribing does not configure the next operation; choose recipients, conditions and actions separately.
Operation details
The inventory includes record, configuration, visitor and background flows. IDs support Era/automation; not every row is a menu button. Asterisks mark required inputs. Unmapped rows do not imply a visible control.
| Operation and ID | Inputs | Permission | Screen or flow |
|---|---|---|---|
Send a form from the website · forms.submit | Form *, Answers, Form details | Write | Record/API/visitor flow; no separate screen button mapped |
Create or edit a form · forms.save_form | Form, Address *, Title *, Creates, Table, Form view, Description, Thank-you message, Consent the visitor must give, Send them to, Behaviour, Answering | Manage | /forms, /forms/[id], /tables/[tableId] |
Set a form’s fields · forms.set_fields | Form *, Fields * | Manage | /forms/[id], /tables/[tableId] |
Stop a form answering · forms.close_form | Form * | Manage | /forms/[id] |
Record a retried submission · forms.record_retry | Submission *, Record type, Record, Why it failed | Manage | Record/API/visitor flow; no separate screen button mapped |
Discard a failed submission · forms.discard_submission | Submission * | Manage | /forms/[id] |
Export submissions · forms.export_submissions | Form *, Only | Export | /forms/[id] |
Related guides
Settings
Options, screen paths and defaults.
Workflows
Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.
Marketing
Marketing — modules and detailed settings
Technical sources
packages/os-kernel/src/modules/forms.ts, packages/os-kernel/src/modules/index.ts, apps/studio/lib/os/navigation.ts, apps/studio/lib/os/settings-groups.ts, apps/era-station/apps/web/src/era/business/screens.ts.