Thanks for the reply. The article states that the feature is available when the form is setup with a login. The screenshot you have provided is for a success message after submitting the form which doesn’t apply to the request which is about re-directing them if they do not have access to the form.
In our scenario, the form (created using the form extension) is a link within the portal menu. The user is already required to log in to the portal and it would not be a good user experience for them to have to login again to access the form (which is embedded in the portal) after already logging in to the portal.
The portal allows the user to view and edit their records, and the form above allows them to create new records. We want users who have a certain setting in an Airtable field to access the form which creates new records.
I realise I can simply set all of the fields to conditionally show based on the Airtable field but when you have 50 fields in the form with that number more than doubling in the future, it is counterintuitive. The simpler and better option would be for the user to access the form according to the setting in an Airtable field.