Setting up user passwords in Knack can be tricky, especially if you are trying to avoid sending credentials by email. Knack does not provide a native or secure method to share passwords with users directly. While self-registration works in some cases, it often does not meet the needs of more structured setups, such as connecting users to specific customers, clients or projects.
In this video, I will walk you through a more secure solution that makes use of Knack’s built-in password reset functionality. With this approach, you can associate users with the correct records and then allow them to create their own passwords, all without exposing sensitive login information.
Thanks to Ian Crowe @KnackPros for sharing the CSS.
Before last month, to send the connection email, I had a check box INSIDE a User Profile form… And it was problematic as it stays checked after saving the form…
The great solution is an Action Triger outside the form. I think you have it this way too.
ps: if you not have one already, it would be useful a video about, as you said very fast, adding fields at the Account level and not at the Roles level. I bet all beginners have a very hard time learning the reasons of that.
Hola @MichaelG. Gracias por los comentarios positivos sobre el vĂdeo. Las grandes mentes piensan igual
He visto bastantes aplicaciones meterse en problemas con demasiados “campos personalizados” en los roles de usuario. Parece que ha nacido una nueva idea para un vĂdeo… gracias.
Hi @MichaelG - thank you for the positve feedback on the video, great minds think alike
I have seen quite a few applications get into a mess with too many “custom fields” in user roles. It sounds like a new video idea has been born…thank you.
