On the User Configuration page, you can specify how users will interact with your app.
Your application is protected by sign-in. You can restrict sign-in to specific Google GSuite domains or users.
You can view and administer registered users in Users > Registered Users. You can delete users, remove authorizations, or add user settings as necessary.
Each data connection in your application can either reference a production key that you have provided or expect signed-in users to provide their own key. Check the appropriate boxes under Require users to authenticate with these data connections. For the rest, navigate to Deploy > Production Keys and click Add key.
For applications requiring user-specific configuration, you can define a user settings schema at Users > User Configuration > User settings schema. Settings marked with
Show on user settings page will be displayed on the app's user settings page, along with any required data connector authentication.
Below are examples of how you might use different types of inputs:
Settings can be hidden from the user by unchecking
Show on user settings page. Some example use cases for hidden settings are: programmatically storing the user's Slack username from their credential, or having a hidden setting to mark certain users as power users (and using the Registered Users interface to manually toggle the setting).
Your development environment interface for these settings, identical to what your users will see, is found under Code > Development > Auth & user settings.
options type to limit the user's input to a set of options. The selected operation will return an array of objects, each with properties
api.isAuthed("<data connection>") and throwing an error if they are not.
User Setting Optionstemplate
If your application requires more customization than the automatically-generated user settings page provides, you can select
Use a custom page template (advanced).