Every Airtable Field Type, Rendered Properly
Attachments, linked records, rich text, durations, rollups and the rest. Every Airtable field type is supported, and editable wherever Airtable accepts a write.
The quickest way to find out whether a portal tool really supports Airtable is to give it a base with attachments, linked records and a rollup in it. Text and dates are the easy part. Support gets patchy after that: a linked record that arrives read-only, an attachment link that expires, a field type that is simply not handled.
CollabPortals supports all 33 Airtable field types, and renders each one as what it is.
What it does
Fields Airtable lets a portal write are editable with the right input for the type:
- Attachments upload and display as files and images
- Linked records are pickers over the linked table, not raw record IDs
- Selects are dropdowns with your options, dates use a date picker, ratings are stars
- Currency, percent, duration and barcode each keep their own formatting
The rest are read-only, either because Airtable computes them or because Airtable will not accept a portal write to them: formulas, rollups, counts, lookups, AI text, buttons, auto numbers, created and modified time, created and modified by, collaborators and sync sources.
Why it matters
Field types are how meaning survives the trip out of the base. A rollup that reads as a number is a total; the same value as text is a string that no longer adds up. A linked record that stays linked keeps the relationship; flattened to a name it becomes a coincidence of spelling.
For the people using the portal, it is simpler than that. They get a date picker for a date and a file upload for a file, which is what they expected.
Two behaviors worth knowing
Rich text is edited in a Markdown textarea rather than a formatting toolbar, because Markdown is how Airtable stores the value. What you type is what the base holds.
Some types start hidden, existing in field permissions with View off until you turn them on: linked records, plus count, button, AI text, sync source, collaborator, rich text, barcode and duration. Collaborator fields in particular can expose a colleague's email address to portal users, so they are a deliberate decision rather than a default.
A field type Airtable adds in future stays invisible until it has been classified here, so the set fails closed rather than publishing something nobody has looked at.
How it works
Nothing to configure: the type comes from Airtable. What you decide is visibility and editability per role, in field permissions. The supported field types reference lists every type with how it renders in view and edit mode.
Who it is for
Bases that use Airtable properly, which is to say most of them: insurance portals with document attachments, inventory with rollup totals, and CRM portals built on linked records.
Try it on your own base
Connect Airtable, build a portal, and share it. Seven days free, no card needed.
Related guides and examples
Field Permissions Down to the Single Column
Control each Airtable field separately, per role: whether it is visible, whether it appears on the create form, whether it can be edited, and whether it is required.
FeatureLet Portal Users Create, Edit and Delete Records
A portal is not read-only. Give people permission and they add records, update their own, and delete them, writing straight into your Airtable base.
Use caseInsurance
Give agents, brokers, and clients a secure portal to submit applications, track policy status, and manage underwriting data, powered by your Airtable base.
GuideNew Feature: Rename the Words Your Airtable Portal Uses
Set what one row is called on any table and your portal rewrites itself around it, from the create button to the delete prompt to the empty state.