We have released a new feature that enables you to easily authenticate your application end users via their Betty Blocks platform account. Using this feature saves you valuable time, as you don’t have to worry about login flows, password reset flows, and all other authentication-related things.
From today*, after creating a new application it will contain a default authentication profile, called "Betty Blocks account". With this new profile, we enable you to easily authenticate the end user of your Page builder pages. We do this by authenticating them via the default Betty Blocks platform login mechanism. This means the pages which are protected by this profile can only be visited by people with a valid Betty Blocks platform account who are added as a builder or user to the application (documentation about authentication profiles).
Update: If you don't see this profile in your application please contact us, we will then add it.
How to use this authentication profile?
Enabling the Betty Blocks Account Authentication profile is trivial. When creating a new page, simply select the Betty Blocks Account as authentication profile in the create page flow, and the page will automatically be protected with the Betty Blocks platform login. This can be done out of the box, no additional setup or configuration is required. The authentication profile also works together with (private) actions and data model filter rules.
*Only new applications created from 15-02-2023 will have his authentication profile available by default. If you would like to have this authentication profile in any of your existing applications, please contact us. |
User management for this authentication profile can be done via the My Betty Blocks application user management:
This feature is mainly powerful for applications aimed at internal usage (so apps with end users inside your company). If these applications contain admin (or private) parts they usually should be protected from the rest of the public app. By using the “Betty Blocks authentication” profile for these use cases you don’t have to build a full authentication flow yourself (e.g. a register flow, a password reset flow, and a user management portal/flow) and can just focus on the actual application content.
That was all for now, your feedback allows us to continuously improve our product. Please, let us know what you think about it. Happy building! 😃