new
All Plans
Internal Form View
The Form View has been redefined. It is now a view type linked to an underlying source form, rendered in ready-to-fill state for any table member with view access. Service desks placing an intake form in every team's view panel, HR teams attaching onboarding forms to people tables, and GRC programs putting attestation forms next to control records all get a one-click submission surface inside the work they already do.
Key Highlights
- Submittable, Not Just Editable: The Form View now displays the linked form in a ready-to-fill state for every table member with view access, not just Solution Managers.
- Linked to a Source Form: Pick any internally-shared form from any solution you manage as the view's source. The view stays in sync with edits to that source form.
- Solution Switcher and Search: The Select Form modal shows forms across every solution you manage, grouped by table, searchable, with inline new-form creation.
- Manager Controls: Solution Managers can rename, swap to a different source form, edit the underlying form, or delete the view from the view properties.
- Migration Handled: Existing legacy Form Views are removed from the views panel; Solution Managers should use the new Forms page to edit forms, and create a new Form View only when they want the form exposed for internal submission.
How It Works
- Add a Form View to a table; the Select Form modal appears with internally-shared forms grouped by table across every solution you manage.
- Pick a form (or create a new one inline) and the view links to that source. The view name inherits from the source form by default.
- Any member of the table with view access opens the Form View and submits the form, subject to record-create permissions on the target table.
- A Solution Manager can change the linked form, edit the form's fields via the designer, rename the view, or delete it; only Solution Managers see these controls.
- If the source form is deleted in the Forms page, every Form View that referenced it is removed automatically.
Use this when a form needs to be available inside the team's existing workspace rather than as a public link, especially for high-volume internal submissions like ticket intake, attestation, or onboarding requests.