[Curiousity] How do you structure permissions/access levels on your app?

I’m curious to learn how do you guys structure permission and access control on your app. Bubble’s privacy settings help, but they are quite limited (ie. can’t refer to a users linked thing fields).

Do you have a permission ‘Thing’ with the various access levels? Do you set all your objects with conditionals for each permission level at every single page? How do you differentiate between Read, Write permissions?

Looking for insights here. :slight_smile:

Consider using option sets and their attributes:

Example:
pages: name: “abc”, private? y/n
user types: regular, premium
etc etc
set them to the user object as needed
then build conditionality on page loads, elements, events, etc

Hope this helps :+1:

Thank you.

While option sets are an alternative, as I understand they are not really safe as all options are loaded with the page and could allow a malicious user to access unintended elements, correct?

A combination of actions allow you to protect your app

Thinks like:

  • Option sets structure to act as a permissions and redirecting mechanism
  • Privacy rules for current user, own user, and key data types
  • Element visibility conditions
  • Page loading conditions

Following a couple of interesting videos from users like @evanlitttle and @TipLister that have kindly shared part of their approach. You can also explore the forum for discussions on this subject.

2 Likes

Cool, thank you for your suggestions!

Seems like it is indeed a combination to achieve a secure app. Will look into it.