Embed Your Portal Inside Your Own Site
Turn on iframe support for a portal and embed it in your own website or app, listing the sites you will embed it into.
Sometimes the portal should not be a separate destination. If you already have a members area, a client dashboard, or an intranet page people go to, sending them somewhere else is a step they will forget.
Embedding puts the portal inside a page you already run.
What it does
A portal can be embedded in an iframe on sites you nominate. In the portal's settings you list the sites you will embed it into, one per line, each starting with https://. That list is the switch: leave it empty and iframe support stays off.
- The portal renders inside your page, with your surrounding navigation intact
- Portal users log in inside the iframe, exactly as they would on the portal itself
- Permissions, roles, and record scoping behave identically to the standalone portal
- You name the sites explicitly, rather than opening the portal up to anything
Why it matters
An embedded portal is one less URL to explain. People who already sign in to your site find their records on a page they know, instead of following a link to a domain they have to recognize.
It also keeps the work small. You are not rebuilding the portal's interface in your own app or maintaining an API integration to pull records across; the portal is doing what it already does, framed inside your page.
How it works
Add the sites you will embed into, then drop an iframe pointing at your portal URL into the page.
Two behaviors are worth knowing before you ship it.
The login session is issued per embedding site. Signing in inside the iframe is a separate session from signing in on the portal directly, so a user who is signed in on one is not automatically signed in on the other.
The sites you list are also allowed to call that portal's API directly, so list only sites you control. Note that the list is not what stops other people from framing your portal, since any site can already put a public URL in an iframe. What it decides is which sites the portal will accept direct API calls from.
Who it is for
Teams that already run a customer-facing site and want records to live inside it: membership organizations with a members area, agencies with an existing client dashboard, and anyone whose portal should be a page in their product rather than a destination beside it.
Try it on your own base
Connect Airtable, build a portal, and share it. Seven days free, no card needed.
Related guides and examples
Serve Your Portal on Your Own Domain
Put your portal on a domain you own, like portal.acme.com, with one DNS record and an automatic TLS certificate. Included on every paid plan.
FeatureYour Logo, Your Colors, Your Favicon
Brand the portal so end users see your company, not ours: a logo in the header, primary and background colors, and a custom favicon on the browser tab.
Use caseMembership Management
Give your members secure, self-service access to their profile, roster, and account data in Airtable. No extra seats, no member login headaches.
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.