Help

Re: Allow unrestricted access to shared forms

Solved
Jump to Solution
773 0
cancel
Showing results for 
Search instead for 
Did you mean: 
MichaelJS
4 - Data Explorer
4 - Data Explorer

We are looking to enable users outside our domain (parents of our students) to submit a form with an attachment. If we turn on the setting "Allow unrestricted access to shared forms" at the org level what other impact might that have from a security perspective? We are using AirTable to manage very sensitive data about our students.

 

Thanks!

1 Solution

Accepted Solutions
Ben_Young1
11 - Venus
11 - Venus

Hey @MichaelJS!

In the abstract, there are three things I keep in mind when it comes to security and shared Form views.

  1. Creating versus editing: Form views do not allow you to edit existing data within a base or table(s).
    They only facilitate the creation of new records.
    While it's technically possible for a malicious actor to spam the creation of new records, you could implement a few form design decisions that would discourage or impede someone's ability to spam record creation and buy you enough time to catch the "attack" before it resulted in the creation of additional dirty data.
  2. Linked records: If your form exposes a linked record field, someone filling out the form would be able to see the primary field values of all of the linked records in the related table. In my opinion, this is the biggest risk. However, it's only really an issue if your linked records' primary field contains any PII or otherwise sensitive data.
  3. Validation & Audits: There are a few nifty tricks that you can use to implement an automated validation and review process of submitted forms. This really just depends on your comfort level with Airtable as a whole, but it's definitely possible.

With those things in mind, you're not putting too much at risk if you do a bit of planning and document where the potential risks are for your specific usage.

See Solution in Thread

2 Replies 2
Ben_Young1
11 - Venus
11 - Venus

Hey @MichaelJS!

In the abstract, there are three things I keep in mind when it comes to security and shared Form views.

  1. Creating versus editing: Form views do not allow you to edit existing data within a base or table(s).
    They only facilitate the creation of new records.
    While it's technically possible for a malicious actor to spam the creation of new records, you could implement a few form design decisions that would discourage or impede someone's ability to spam record creation and buy you enough time to catch the "attack" before it resulted in the creation of additional dirty data.
  2. Linked records: If your form exposes a linked record field, someone filling out the form would be able to see the primary field values of all of the linked records in the related table. In my opinion, this is the biggest risk. However, it's only really an issue if your linked records' primary field contains any PII or otherwise sensitive data.
  3. Validation & Audits: There are a few nifty tricks that you can use to implement an automated validation and review process of submitted forms. This really just depends on your comfort level with Airtable as a whole, but it's definitely possible.

With those things in mind, you're not putting too much at risk if you do a bit of planning and document where the potential risks are for your specific usage.

MichaelJS
4 - Data Explorer
4 - Data Explorer

Thanks, Ben. That's helpful. I'm looking into SSO as well, since the folks we want filling out the forms already have users accounts in our CRM.