I’m building a fitness app in Adalo where personal trainers need to view and update their clients’ exercise plans, weights, etc., from the client’s perspective. Ideally, they could hit a “View as Client” button and the app would behave exactly as if the client themselves had logged in—without ever exposing or storing plaintext passwords.
Is there any undocumented trick, workflow, or best practice in Adalo that would allow a trainer to “log in as” or “impersonate” their client—without refactoring every screen or exposing passwords? Any ideas or alternative patterns would be hugely appreciated!
There are many ways to do it, not exactly impersonating (which i dont really know how to do it).
Two simple ways i see are:
1 - Create a “Mini-CRM” where the personal trainer see his/her adepts and go to extra screens to edit info. That can be donde with a boolean in users where have Client on/off, Personal Trainer on/off and Admin on/off which is you. In this way you send each user to the designated dashboards/CRM.
2 - Create the booleans i have say before and put extra inputs whenever you want to change info and allow to being shown to the designated “permission” level.
EDIT: See, reveal, check users password may incur in an illegal action.
I hope it give you a hint about how to start.
Kind Regards
Jare Ramirez
Yep this is probably the one, I’d just need to replicate relevant screens and there are not many, so shouldn’t be over complexed.
I’ve researched this option a little more and although it will work, on other hand it will give a compliance hell and possible issues with GDPR, as most of my clients are UK based. @JareRamirez is right, it’s basically illegal
Thank you both for looking into it! I’ll use both of your advices when developing this feature.