Creating App Users
App Users are the users authorized to sign in to the app by an account Administrator (i.e. you). Once signed in, the specific Services they are authorized for will be downloaded to the app on their mobile device and refreshed each time they sign in.
How to Create an App User
1. Click the ‘App Users’ link on the top navigation menu. Then click “Add a User”.
2. Choose a username type:
a. Email address
When using email addresses, your mobile app users can create and manage their own passwords and use the Forgot Password functionality. They can use “Sign in with Google” if they are signed up using their Google account. You can also set up SSO integrations for quick and seamless logins. A generic email address can be used if multiple people use the same device.
b. Plain text usernames
Instead of email addresses, plain text usernames are also available. These are useful when you don’t know the app user’s email address or to relate the app user’s scans to an activity, location, etc. instead of a person. With plain text usernames, you control the app username. Note: There are other ways to capture an activity or location with each scan so you don’t have to always use the app username for that.
[OPTIONAL] Authorize the app user for any or all of your services. (Also, you can add services to users later).
[OPTIONAL] By default, the app user can have unlimited mobile devices. Also, whenever the user signs in to a device, that device is “activated”. Check the “Set limit device” box to limit the user to the desired number of mobile devices
Adding App Users when Creating/Editing your Service(s)
When creating or editing a service, you can add app users to any service on the Users step. On the CodeREADr mobile app, once you assign a user, the service will appear upon signing out and back in or refreshing the Services screen. Note: any user not added to this User list will not be able to see this service in the mobile app.
Managing App Users
To add or edit many app users simultaneously, use the IMPORT USERS option on the App Users page.
Notes:
1. You cannot have column headings. They are shown here for reference only.
2. You can download your current list of app users as a CVS file for editing and re-uploading. Passwords are never included in the download.
- If you add a plain username (i.e. text, not email addresses) for a new app user, you must include a password in the uploaded CSV file.
- If you use email addresses as the username, passwords are handled as follows:
- For accounts created before June 27, 2024, there is a transition period until end-Jan 2025 where you can still set email address passwords for uploading CSV files and when using the API. Newly added email address owners will not be emailed.
- For accounts created on or after June 27, 2024, you must leave the password field blank. Email address owners will be emailed for them to create and manage their passwords.
- Starting Feb 1, 2025, all new email app usernames will be emailed for them to create and manage their passwords. Alternatively, to use admin-controlled email addresses you can elect to use SSO or Sign in with Google.
3. To delete an app user, you need ‘delete_approved’ in column 5. If that column is, blank the system will assume you want to keep or add that app user.
4. For the Device Limits:
- ‘0’ means there is no set limit.
- ‘-1’ means the app user has no access.
- ‘1’ (or greater) means the app user can sign into 1 device (or the number specified here).
If the device limit field is left blank for a new app user, the default ‘0’ (unlimited) will be applied.
5. The User ID column should be blank to create a new app user. The system will create a User ID for that new username.
6. You don’t need to include existing app users in the file unless you want to make a change or delete them. If you do include them, you need to include the current User ID in that column. Blank cells will be considered “no change”. You cannot change the username if you use an email address app username.
7. Save your file as a comma-delimited CSV file for uploading.
8. Errors in your upload can be seen here. Changes or additions made in the CSV file will have been applied unless shown as an error. Before re-uploading you can optionally remove accepted changes so they don’t show an error that they have already been added or changed.
Sign in with Google
Companies that have Google accounts with email addresses can allow their app users to sign in with their Google account’s email address. You can disable that option in Settings.