Live Airtable Data, With No Copy and No Sync

A whole class of portal tools copies your data before it shows it to anyone. You import, you map fields, and from then on you have two versions of the truth and a sync job between them. When the sync lags, someone reads a stale number and acts on it.

CollabPortals keeps no copy of your records. Your Airtable base is the database. Every page in the portal is a live read, and every edit a portal user makes is a write straight back into the base.

What it does

You connect your Airtable account once through OAuth and choose which bases CollabPortals can see. From then on, CollabPortals reads your tables and fields directly through the Airtable API, and reads and writes records the same way.

A portal user opening a page triggers a read. A portal user saving a form triggers a write. Someone editing the same record in Airtable sees the portal user's change, because it is the same record.

• No import step and no field mapping to maintain
• No second database holding a copy of your records
• Changes made in Airtable show up in the portal, and the other way round
• Automations, views, and formulas in your base keep working exactly as they did

Why it matters

Your team keeps working in Airtable. That is the point. Nobody has to move into a new tool, learn a new interface, or remember which system is authoritative this week.

It also means the rest of your Airtable setup keeps its value. Formulas still calculate, automations still fire, and the views your team works in are untouched, because the base has not moved. The portal builds its own views over the same data, so what your team sees in Airtable and what your customers see in the portal are configured separately.

And when you stop paying us, your data has not gone anywhere. There is no export to run. It was in your Airtable base the whole time.

How it works

Connecting takes one round trip through Airtable's OAuth screen. You pick the bases to grant access to, and Airtable lists the permissions CollabPortals is asking for before you approve: reading and writing records and their comments, reading and writing base structure, and your account email. Access is limited to the bases you pick.

Tokens refresh themselves. When one expires, the next request refreshes it and carries on, so nobody has to reconnect on a schedule. Revoking access in Airtable stops your portals, and reconnecting brings them back. Adding a new base later is a reconnect, not a rebuild.

The full walkthrough, including what to do when a base does not appear, is in the connecting Airtable guide.

Who it is for

Anyone whose data already lives in Airtable and who needs people outside the base to see part of it. Client portals, contractor compliance, and inventory management all run this way: one base, several audiences, no copies.