Both the Form and Portal extensions can perform similar functions. They both allow users to log in and see/update their data. The main difference is how the data is displayed on the screen.
💡 Tip: The Portal is ideal for scenarios requiring user authentication and frequent updates. Use it when users need to log in to manage multiple records or interact with complex data relationships. Portals excel at displaying filtered data, giving users a tailored view of only the information they need).
There is a lot of overlap in the features available in both extensions. You can use either one in most use cases. But here are the main differences:
| Portal | Form |
Default view | Multiple records | Single record |
User-friendliness | Average | Simple |
Note that almost the entire form extension is built into the portal. In many cases, several forms in the same base can be replaced by one portal (or a shared view, if you don't require a login), for example by using the form view functionality.
Portal
In the portal, you can display the data as a list of records (or grid/gallery). It makes more sense to use the Portal extension if your average user is going to edit/create records across multiple tables or when you want to present them with all records related to them in one view, e.g. all invoices for a certain client.
The Portal is one of the extensions that offers the ‘Inline Editing’ feature. This feature allows users to edit records directly within the grid view, similar to how records are edited in Airtable.
Form
In the form, the data is displayed on a long vertical card. Classic use cases include signup forms, payment information forms and many more. Because you can add a login page to the form, the user can look up a record (e.g. themself, a product, etc.). You can also allow users to see records from multiple tables by including in your form linked records fields (displayed as a list). This allows users to add/edit multiple records that are linked to them.
