I fully expose my app’s features only for those users that “email confirmed” is “yes”, the problem is that i have a bunch of users that’s being signed up by myself on behalf of the user, and its not appropriate to send them thru a confirmation email, because i know they own this email because otherwise they wouldn’t have the temp. password to access?
How can i check their “Confirmed” as “yes”
If you know that they own their emails, is it necessary to have the users to confirm them? Otherwise, when they have changed their password, you could send the confirmation email.
no its not, that’s exactly my point
Sorry, I don’t understand your problem then.
Question rephrase: if a user wasn’t sent a confirmation email at all, does bubble return this user’s “email confirmed” as “yes” or as “no”?
Don’t know, really. Try it with a user.
Just tested, it is considered as “no”, which doesnt make sense to me
I think this makes perfect sense.
There was no email for them to comfirm, but an email might be sent out
So how would you deal with problem above?
Send them the e-mail (which they have to click), thus giving them the ‘email confirmed’ is “yes”. Or create your own yes/no field (called FullAccess, for instance) on User to identify users that were signed up by you, then change your logic for full access to ‘email confirmed’ is “yes” or User’s FullAccess is “yes”.
But i have another AND condition for giving full access, and in bubble having an AND together with an OR condition is a problem because if i write for example: Only if User is an employee AND confirmed is yes OR “Fullaccess” is yes, how will bubble intemperate it?
There are 2 ways to intemperate this:
Are you talking about table level security (privacy) or Workflow level?
If you are talking about a workflow level AND if I understand you clearly, then you could split your conditionals just to be sure into two Workflows.
In the On Page Load page set a conditional (User IS NOT Employee) then in the Workflow item (NAVIGATE TO PAGE) kick them out.
In another On Page Load page set conditional (User IS NOT Confirmed AND User IS NOT All-Access) then in the Workflow item (NAVIGATE TO PAGE) kick them out.
Depending on the security requirements this might not be the best strategy, there are others ways to do this. For example you could in the first workflow item on the page load SET STATES so if (A and B) then SET STATE FLAG1 = TRUE then compare FLAG1 to Employee and do accordingly.
This would be more convenient if you want to hide and show page elements selectively. So you could compare FLAG1 and Employe in the Conditional tab of an elements such as a repeating group, a button, a text field etc etc.
Rick
Independent Developer
no, this condition is for certain elements to be visible or clickable
Then please read the last part of my message, it covers that.
I am also not getting any confirmation email of bubble.is
Sorry for the late response. The way I’ve gotten around the multiple conditions is to use a custom state. Let’s say you call it FullAccess and have a default value of “No”. When the page is loaded check if User is an employee AND confirmed. If so, set the state to “Yes”. Then do your second check for User’s FullAccess is “yes”. If so, set the state to “Yes”. Now, you only need to point your conditionals to the custom state being “Yes”.
Big caveat here - always assume that any user (whether logged in or not) can view anything they want on your page. Anyone can look into the code on your page and change its visibility temporarily, so never expose sensitive data in a hidden container and assume it’s safe. If you have not looked into data privacy, I would suggest you do.
Hope this helps!
Kirk
@mente12 I missed the last part of your message too and read it after I replied! Great minds and all that … 
This topic was automatically closed after 70 days. New replies are no longer allowed.
