Looks nice for fine-grained access-control. In your example, the "Salary" label remained in the UI. Is it possible to detect that the data is private and to either remove the label or insert "" in the place of the data?
I know its been 2 years. But i bealive the server just does not send the data if you dont fullfill that prerequisit. Lets say i am the owner of the account, then the server sees i am logged in, therefor sends all the data i am allowed to see in that particular page. On the other hand if i was logged in with another account, then server would only send certain data
Awesome. How about when I want to grant access to workflows, but not to others? E.g. maybe I want to be able to use their address for regional sorting and/or distance calculations, but I don't want to grant others the specific address?
But how is this done to prevent access to entire pages , not just variables ? (great video, but interested in how the paywall can be built to prevent page access to non-payers)
Thank you for the tutorial! Can you tell the difference between "this user is current user" and "current user is signed in"? What will be the difference in terms of privacy rules?
'this user is current user' refers to what the 'current user' has access too. i.e If I'm logged in as the 'current user' I should have access to all of my own data. 'Everyone else' should have access to limited data.
Thanks for sharing. It cleared my doubts about user privacy. Tutorial is well made. Hope to see more.
Bubble really need to put those checkboxes on the left side of the label! (Looking at the Fields dialog box... confusing!)
Haha, agreed!
10000% I always get confused with that.
Looks nice for fine-grained access-control. In your example, the "Salary" label remained in the UI. Is it possible to detect that the data is private and to either remove the label or insert "" in the place of the data?
I know its been 2 years. But i bealive the server just does not send the data if you dont fullfill that prerequisit. Lets say i am the owner of the account, then the server sees i am logged in, therefor sends all the data i am allowed to see in that particular page. On the other hand if i was logged in with another account, then server would only send certain data
Awesome. How about when I want to grant access to workflows, but not to others? E.g. maybe I want to be able to use their address for regional sorting and/or distance calculations, but I don't want to grant others the specific address?
But how is this done to prevent access to entire pages , not just variables ? (great video, but interested in how the paywall can be built to prevent page access to non-payers)
Thank you for the tutorial! Can you tell the difference between "this user is current user" and "current user is signed in"? What will be the difference in terms of privacy rules?
'this user is current user' refers to what the 'current user' has access too. i.e If I'm logged in as the 'current user' I should have access to all of my own data. 'Everyone else' should have access to limited data.
@@Buildcamp Thank you for the explanation! Is there any difference between " this user is current user' and 'current user is this user'?
thank you !