Skip to main content
Question

Best way to share individual records with external users?

  • September 23, 2026
  • 3 replies
  • 17 views

Hello,

We utilize Airtable to organize our service center jobs within a university setting. One issue we continually run into is there is no way for us to share the job status, or any updates to the record status, with the submitters once it is in our Airtable instance, short of sending emails. Airtable Portals does not work well for our needs, as we have 100s, if not 1000s, of unique job submitters yearly. Some submitters have only one job come through our system, others have dozens. 

What I would love is a way for submitters to see a job ‘ticket’ where they can view any updates to their job status - what the current ETA is, if it is still under review or actively being processed, etc. They don’t need to be able to interact, just view selected data under the record. 

We have a budget I could utilize to pay for an extension, but paying per ‘submitter’ doesn’t makes sense given we have so many unique, one-time submitters. Any thoughts on the best options given our use case? Thank you!

3 replies

Mercerntino
Forum|alt.badge.img
  • Participating Frequently
  • September 23, 2026

Hi Livia, for your use case, I’d look at creating a lightweight external “job ticket” experience rather than giving each submitter direct access to the Airtable base.

Each submission could generate a unique tracking link/ID that takes the submitter to a read-only page showing only their job: current status, ETA, updates, and other selected fields.

That way, someone who submits one job doesn’t need to become an Airtable collaborator or see other records. For hundreds/thousands of one-time submitters, I’d also compare the cost of Airtable Portals against a lightweight external portal connected to Airtable before choosing the architecture.

The important part would be making sure each tracking link can only expose the submitter’s own record


DisraeliGears01
Forum|alt.badge.img+22

I have something like this in production (sharing a “ticket” with non-logged in users) but I use Fillout as basically the display portal. 

The submitters use a create ticket form through Fillout to generate a ticket (this is for interpretation requests, but the concept would generally be the same) and then they receive via email a link to their ticket, which is a Fillout edit record form. You can use @ functions in Fillout to display record information (making it non-editable), though you would need an editable function to make it a “form”. In your case this could be a Cancel ticket checkbox or maybe just a free text “Updates” box for the end user to add more information as necessary. Regardless they would see any progress updates you make on the backend in Airtable displayed on their ticket. Fillout is pretty affordable and doesn’t charge per submitter.

There might be a way to do this via Airtable interface too, but this is what comes to mind as I’m actually running this currently. 


ScottWorld
Forum|alt.badge.img+35
  • Genius
  • September 23, 2026

As ​@DisraeliGears01 mentioned above, the easiest & simplest & quickest way to do this is to use Fillout’s advanced forms for Airtable, because it lets your submitters view (and optionally edit) an existing record by giving them a unique URL for that record.

As ​@DisraeliGears01 mentioned, just use the @ symbol to add read-only fields to your update form.

You can even create a login page to add security to your form.

Fillout is 100% free (for up to 1,000 submissions per month), and it offers hundreds of features that Airtable’s native forms don’t offer, including the ability to:

I show how to use a few of the advanced features of Fillout on these 2 Airtable podcast episodes:

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld