CollabPortals

Record Embeds

Show pages from other sites on each record, such as a per-record form or ID check, read from a field and shown only when your conditions match.

Overview

A record embed shows a page from another site inside a record's page in your portal. The link comes from a field on the record, so each record can show its own page.

The usual case is a step that happens somewhere else. An Airtable automation creates an ID check, an intake form or a signature request with the provider, and writes its link into a field. The record page then shows that form, and hides it again once a status field says it is done.

Setting It Up

  1. 1

    Open the page's Display tab

    In the portal admin, open the page and switch to the Display tab. The "Record Embed" section is at the bottom of the tab.

  2. 2

    Add an embed and pick the URL field

    Click Add embed, then pick the field that holds the link. URL fields, single line text fields, formulas that build a link, and lookups of a URL or single line text field are all offered.

    The field can be one end users can't see. Its value is only used for the embed and is never listed on the page.

  3. 3

    Add the sites you allow

    Add every site the links point to, such as forms.example.com. Use *.example.com to allow every subdomain of example.com. You can paste the provider's full link and we keep just the site.

    Nothing shows until at least one site is listed.

  4. 4

    Add conditions (optional)

    Conditions decide which records show the embed, for example "where KYC Status does not equal Verified". Conditions can use fields end users can't see.

    With no conditions, the embed shows on every record where the URL field has a link.

You can also set a heading, a height, and whether the embedded page may use the camera and microphone. Turn that on for ID and selfie checks, and leave it off otherwise.

Settings save with the rest of the portal configuration.

More Than One Embed

A page can have up to five embeds, for workflows with more than one external step. Each has its own link field, its own allowed sites and its own conditions, so an ID check and a contract signature can come from different providers.

Every embed whose conditions match is shown, in the order they are listed. To show one step at a time, give them conditions that can't both be true: for example the ID check while "KYC Status" is not Verified, and the contract while it is. Use the arrows on each embed to change the order, and the switch on each to turn one off without losing its settings.

What End Users See

Each embedded page appears on the record's Details tab, below the fields and above any related records.

  • A link to an allowed site is shown inside the portal, with an "Open in a new tab" link under it.
  • A link to any other site is shown as a plain link naming the site, not embedded. The same goes for a plain http:// link, since a secure page can't embed an insecure one.
  • No link, or conditions not met: nothing is shown.

When a status changes, the embed updates the next time the record page loads.

When the Page Is Blank

Some sites refuse to be shown inside another site, and many identity-check and e-signature providers are among them. When that happens the embedded area stays blank, and the browser gives the portal no way to know.

That is why the "Open in a new tab" link is always there. If your provider refuses, check its settings for an "embedded" or "iframe" option and add your portal's address as an allowed parent. Some call this an allowed domain or a frame-ancestors setting. Otherwise, end users can use the link.

Security

  • Only sites you list are embedded. A link to anything else is shown as a link, so end users can see where it goes.
  • The embedded page can't navigate the portal away or replace it.
  • The camera and microphone are off unless you turn them on.
  • End users never receive your settings: the list of sites, which field holds the link, or your conditions. The portal works out what to show before the page is sent.

The embedded page belongs to the provider, and so do its privacy terms. Showing it inside the portal tells the provider which end user opened it, the same as following the link would.