How to protect sensitive parts of your Bubble app

Подписаться 19 тыс.

Просмотров 1,2 тыс.

50% 1

Discover how to secure your Bubble app by implementing user role-based access controls. This tutorial will guide you through setting up roles, managing permissions, and ensuring that only authorised users can access specific pages or features within your application.
⏱️ Timestamps:
00:00 Understanding security risks
06:44 Understanding Client-Server Relationship
12:03 Securing Workflows and Actions
15:27 Redirecting Unauthorized Users
22:02 Understanding HTTP Requests and Responses
31:21 Securing Your Bubble Application
45:25 Conclusion and Final Thoughts
📖 What You'll Learn:
- The fundamentals of setting up and managing user roles within your Bubble app
- The difference between the client and the server
- Protecting server side actions
- Techniques for controlling page and element visibility based on user permissions.
How to use Bubble’s privacy rules to protect your app’s data effectively.
🔗 Useful Links:
The Ultimate Guide to Bubble Security:
gumroad.com/a/301410515/krzuz
Basis Foundation Template:
bubble.io/template/basis-foun...
Bubble Privacy Documentation:
manual.bubble.io/core-resourc...
👩‍💻 Who Should Watch:
Bubble developers and app builders looking to enhance the security of their applications.
Anyone interested in implementing advanced access control mechanisms without coding.
🔥 Tips:
Leverage Bubble's built-in features for dynamic content visibility and action permissions.
Regularly review and update your app’s privacy rules as part of your security strategy.
Test your app with different user roles to ensure that access controls are working as intended.
❓ Questions or Feedback?
Drop your questions in the comments below, and we'll be happy to help!
If you find this video useful, don't forget to like, subscribe, and share with others who might benefit.
#Bubble #saas #UserRole #PageAccess #WebSecurity #BubbleTutorial #NoCodeSecurity

Опубликовано:

27 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 13

@RaymondGroenewald 4 месяца назад

Such a great and elaborate explanation. I've seen so many questions around this and you've explained it perfectly. Thanks!

@mneary 3 месяца назад

Thanks Raymond!

@BorisMinor 5 месяцев назад

Really well explained, thank you.

@muhammadhaqny 5 месяцев назад

Very informative and useful, keep the good things coming up. Thanks.

@marianradulescu6730 2 месяца назад

Realy great, thank you !

@Lahiru_Ranaweera 5 месяцев назад

Very important lesson. Thank you.

@hustlin_heev 2 месяца назад

Hey Matt this is a very important video, thank you. Just to be 100% explicit and sure - for an app to be secure, you must have when page is loaded -> first action: Direct user to 404 ONLY WHEN Current User is not logged in?

@matthieubouilde2038 5 месяцев назад

Always difficult to make sense of how bubble treat the data, so that's a great video explaining it 👌 What about pages with a type of data ?

@john13285 5 месяцев назад

out of context, but how do you allow users to upload a csv that has comma-separated text values in the cells of one of the columns that are of a data type attached to the main data type (the data type being uploaded as csv)? i read for the native action arrays have to be uploaded as JSON array but the user doesn't know that and simply uploads the file where the values are comma-separated.

@mattschuberg 5 месяцев назад

Great video. Is there a way to get a 302 redirect on a page when you also want to be able to redirect the user to a specific path in your URL after they log in? For example, when a user clicks on a link in an email you sent them but they're not logged in. I want them to be redirected to that specific URL path afterwards. I'm able to do that using "This URL", but it causes the redirect to be a 200 redirect instead of a 302. Is there a better way to do this?

@antoruby 14 дней назад

Great question 😅 Have you found an answer?

@mattschuberg 14 дней назад

@@antoruby Not yet, unfortunately.

@antoruby 14 дней назад

@@mattschuberg Thanks for answering! I also couldn't find a way to use "This URL", but there is a way almost equivalent that still gives 302: Check the "Send current page parameters" and also "Send more parameters to the page" to add something like afterlogin="my-page", where you have to type the "my-page" instead of extracting anything from "This URL". Then just use these parameters to redirect the user back after the login.