This feature allows you to remove the need for users to authenticate into Quickbase to use some of your Form Engine forms, and they do not have to be Quickbase users in your target apps. This means your forms can be used by more people, inside or outside your organization. It also meets a particular need for users in SSO Quickbase Realms, who can only authenticate into Quickbase add-ons using User Tokens.
You create a Supplied Connection (auto-authentication) for any form by creating a User Token for the app the form works in, and embedding that User Token where highlighted in this menu.
(More details if helpful): specifically, you need to create a Quickbase User Token that has the permissions sufficient for your users to use a form the way you intend, and User Tokens convey the Add/Edit/View permissions to a QB app that the QB user who creates them has in the app. So if you create a User Token with your Quickbase login for instance, that token will convey your permissions in the target app(s) to any forms you use the User Token in. Note: this also means that the Record Owner and/or Last Modified By of the QB records added or updated will appear as the creator of the User Token used.
Since a User Token carries the app permissions of the user who created it, we highly recommend creating a new QB user and generating your user tokens from that user. This gives you more permission control over those user tokens that are used in your Form Engine forms, because you only grant that user a Role in your QB apps that convey enough permissions for them to use the Form Engine forms as you intend.
When you digitize a form where you want to use Supplied Connection, you use three “Publish” links in the dropdown menu above to create a URL field in your target table for the form, and then paste your User Token into the Supplied Connection section of the form. For Add Record URLs, you need to use the Publish “Add” Link to create a specific Add Record URL field, because only that field will make use of your User Token, not the generic (non-authenticated) Add Record URL that the Form Engine auto-generates for each form.
Security Note: For Supplied Connection forms, the Form Engine embeds the User Token in the form’s URL string and passes it through to Quickbase to authorize data going into or out of Quickbase in that form. It does not store any User Tokens outside of Quickbase.