This Product Ideas board is currently undergoing updates, but please continue to submit your ideas.

Manage inputs visibility based on the requester account

Showing results for 
Search instead for 
Did you mean: 
6 - Interface Innovator
6 - Interface Innovator
Status: New Ideas
What is the proposed idea/solution?

In forms, we are able to capture automatically the account of the person submitting the form (for logged in accounts). Since this is already a feature in place, it would be important to enable this information as a type of filter to be used to manipulate the visibility of subsequent inputs on the form.

This way, if user John is submitting the response, we can add a filter down the form so that only if user "john" is submitting the form, the field "A" becomes visible. If user is not "john",  field "A" will not be shown.

Note: we are aware that using the manual requester assignment works, but our customers complain that they have to enter it manually, so the improvement is really on using the automated user detection.

How does is solve the user problems?

Big organizations with multiple teams have different requirements according to the different user groups/teams. This simple feature allows to have better control of the information requested without the need to duplicate a form based on different teams, hence, reducing the maintenance/operational costs.

How was this validated?

It is a problem that we have in our organization that we're not able to solve as we don't want to duplicate forms. At the moment we mitigate it with training and adding as many "helper texts" to the forms, however, people tend not to read those helper texts more often than we'd like, and our data continues to be corrupted and we need to manually review all the information and cleanup after, when this quick filter would reduce all of that.

Who is the target audience?

Enterprise customers.

1 Comment
18 - Pluto
18 - Pluto

Yes, that would be a very cool feature to have. In the meantime, here are 3 workarounds that you can use:

1. You already mentioned this in your post above, but you can solve this by having the user manually choose their own name from a drop-down menu. 

2. Fillout’s advanced forms for Airtable already offers the exact feature you’re looking for. It lets you create a login page for your Airtable form, and then you can conditionally show or hide Airtable fields based on the person who is currently logged into your form. Even better, the login page can be optionally synced to a table of users in your Airtable base, so that you can restrict access to just the people that you specify in your Airtable base. And best of all, Fillout offers over 100 advanced Airtable features that are not yet available in Airtable’s native forms. For example, you can display lookup fields, rollup fields, and formula fields on your form; you can update existing Airtable records from a form; and much more.

3. Similar to the #2 solution above, Noloco’s advanced interfaces for Airtable offers the exact same feature. You can show or hide fields on a form based on the currently logged-in user.

p.s. If you have a budget for your project and you’d like to hire an expert Airtable consultant to help you with any of this, please feel free to contact me through my website: Airtable consultant — ScottWorld