Signup, Login, Password reset
The keys to your castle
Last updated
The keys to your castle
Last updated
The openBuild framework comes with a reusable that handles Sign up, Log in, Reset passwords and much more.
The resauble is used on the login page and reset_pw page in the framework.
Sign up with email workflows and UI for social logins.
Workflows connected to Signup section are in the 'Signup' folder.
By default, the new user has to accept the Terms and Conditions and Privacy policy to be able to signup. That's why we use the conditionals logic on the button and pre-built workflows for changing the state.
Two main events connected to the login section are:
a) 'Log the user in' action - that gets triggered directly on the button click. It is placed there to enable the user to submit the login when hitting 'enter',
b) 'LOG IN' custom event - by default, only the redirect action is placed in this custom event, but this is the Workflow where additional actions should be placed. The same custom event is used for 3rd party signup/login.
In the reusable, there is a dedicated section with workflows connected to password reset.
When a user inputs their email we send it to a custom event called '📧 SEND RESET PASSWORD EMAIL'
In the custom event there are 3 actions:
a) Send password reset email - native Bubble action to generate reset password token
b) Send Email - Reset Password Link - a standard email with information about how to reset your password and dedicated link
Section visible after successful submission of the 'Forgot password?' form.
After clicking the link in the email user will be redirected to the Reset password section.
In the framework, you will find two versions of the password strength checker i.e progress bar or displaying password details. Both of them work independently so you can choose one that matches your app, or you can keep using both.
Same as with the Reset Password workflows, there is a dedicated Custom event to handle the actions connected to sending the user magic link via email.
Currently, the reset password activation token is only active for 24 hours from the creation date. This time window is definitely restrictive so we handle invalid tokens via a better User Experience.
In openBuild we take advantage of the error-handling feature that allows us to trigger an action whenever the User tries to use an expired token.
By default whenever a user requests a reset password token via the User Access Management reusable we create a link that contains his email in the URL. If you did send your user a reset password email without the email parameter, the pre-built workflow logic will also handle that user.
openBuild template comes with pre-build validation workflows. To enable them set the verifyEmail attribute in 🔒 System option set to 'yes'.
If you enabled the email verification workflows, after the Signup we trigger CONFIRM-EMAIL custom event.
In the verify page you find two sections.
Remember to correctly connect redirect workflows to your app pages.
Signup workflow triggers a SIGN-UP custom event, that depending on your app settings will trigger a confirmation email sequence or not. Read about it in .
c) Send Email - Activation Link - from the you are able to send user invites to the new users. The email content of that invite is different than a standard Reset Password email.
Additionally in the you find a disabled workflow that needs enabling if you want to block access to the app for every user who does not have his/her email verified.
