There are two types of users in the platform, Team Members who have access to the console, and App users who have access to one or more apps.
For more on Team Members check out the article here.
App users are the people who can access Private forms by logging into an app. Private forms are only able to be accessed by authenticated App users.
Create an App User
1. To add a new App user click the Apps side menu to view the list of apps.
2. Click the Manage button on the app you want to add the user to.
3. Navigate to the User tab.
4. Click the Add User button in the bottom right of the screen.
5. Enter the email address of your user and click save.
Create Multiple App Users
To have multiple users added, you can use the Upload CSV instead of adding individual app users.
1. To have multiple users added, the CSV file needs to contain a list of email addresses, see the example below:
2. With the CSV created, select the Upload CSV button when creating a new app user.
3. Once uploaded, the email addresses of all of your app users will be displayed.
Note: You can choose which users will use Google to login or click the remove button to remove them from the list.
4. Click the Save button to start adding users.
Temporary Password
When a new app user is added to an app they are provided with a temporary password. This is used when first logging into the app. Once the temporary password is used to login the app user will be asked to set a new password. Temporary passwords last 14 days, if the temporary password is not used within those 14 days, then it will expire and a new temporary password will need to be sent to the app user.
Temporary Password Status
When a new user is added to an app the icon next to their user will show as an orange hourglass. This means the user has not logged in to the app and their temporary password has not expired. When the temporary password expires the icon will change to a red padlock. When this happens the user will not be able to login and a new temporary password will need to be sent. To send a new temporary password to the user, click the Resend password button. This will send an email to the app user with a new temporary password lasting another 14 days. Alternatively, the App user can go through the password reset process, this will send the app user a verification code that can be used for the password reset process.
Removing Users
If you would like to remove an App user click the trash icon to the right of their email address. You will be prompted to confirm before deleting.
When adding and removing users you will require the User management permission to be enabled. See the Roles Article for more details.
SAML Authentication
Instead of using the out-of-the-box user authentication, you can integrate with your existing user management service using the SAML 2.0 integration. This can be used to integration with services like Active Directory and Auth0 form more information on them check out their articles.
Google Authentication
App Users are also able to authenticate using Google. When adding a new user make sure to select the login with Google option. This will ensure the app user is not sent a temporary password and the user will be able to login with Google.
Email Sending
You can configure a sending email address for any emails sent from the app, such as the welcome email that is sent to new app users. By default, app emails are sent from [email protected]. Do note that you will need access to the email address you set as the sending email, in order to verify it.
Authenticated Forms
Only App Users can see authenticated forms.
If an App User wants to access an authenticated form they must first login via a login button in the forms library.
Get Help
If you have any questions or would like assistance with setting up your App Users please contact us via this support portal or email [email protected]. We are happy to assist in any way we can.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article