Do we need to always include “When Current User is logged in” on Privacy roles even when setting other User parameters in order to protect data?
For instance, in the example below could I remove the “is logged in” portion in exchange for using a single “Current User’s Admin is “yes””? Will Bubble know to first check if current user is logged in? I am trying to save time when developing future privacy roles (ie: not include “is logged in” on every single instance)
In this case, I would beleive that if your default value for “Admin” is no then a non-logged user will have this field to “no” so there is no need here for “is logged in”.
However, when a non-logged user goes to your website, it has a kind of temporary User object associated to him, so for other cases you might want to check that the user is logged in. For instance on my website I have a profile page for all users. I want any visitor to be able to see some basic info on that profile page (like Pseudo, Profil picture, …) while I want logged user to have access to some more info (for instance a phone number or an email). In that case, checking that the user is logged in is important
