Hello, I am working trough some client requirements for a new GlideApp to develop about field workforce issue tracking, we are facing two key requirements (show stoppers if not solved)
Secure password enabled log in without email account access as field agents very often do not have email accounts available and/or enabled in their smartphones, alternatively they could self identify via WhatsApp/SMS message, is that possible? The password could be provided and updated by sysadmin manually, if that’s feasible.
The app should enable sporadic off-line record adding in case of unavailable cell service coverage, the offline added records should auto-synch when the cell phone coverage is reestablished.
Please let me know if that’s possible and if so how to overcome these challenges.
I don’t think this is available natively, either secure password login or WhatsApp/SMS authentication.
I was thinking of a flow where you utilize a third party tool like Make to generate a random number, then send that to the user’s phone number. The user enters the code in the app to verify and “login”.
But since you have to bring the code back into the app to verify, and since there’s no email to configure “users” and apply row owners/roles, I don’t think that is secured at all.
Per Glide’s Docs: Business and Enterprise users have the ability to add rows offline. Users will be able to view the app, but not make changes to the data other than to add a new row.
Thanks a lot ThinhDinh, however how about the login without pasword, exploring a non-ortodox possibility based on “navigation” for instance the user enters freely in the traditional sense to the app, but then he’s presented to a page with a entry field, only if the user enters a valid number from a hard coded list, the app allows to navigate to other pages, is that possible? The list of hardcoded valid codes could be stored in a google sheet and maintained by the admin? how does this sound? Posible?
It sounds possible to me, but to make it fully secured there’s a long way to go. What I think is:
The Google Sheet must not be connected to the app at all (or bad actors can retrieve the code easily).
Let your user enter the code in the app, but use a third party solution like Make to verify it. If the code is correct, send back a value to the app to let the user access the screen as needed. If not, send another value back to tell them that the code is incorrect.
The user experience will most likely not be as good as you want, but that’s one way I think it can be done securely.