I’m assuming this isn’t a private app? And you need an array column to assign two row owners (the user and yourself) as the owner of the row?
I don’t know to what extent a “banned” user could manipulate the data and override tab visibility, but as long as you are using row owners, they would only have access to their own data anyway. Never tried to hack tab visibility, but I think Mark felt pretty confident about it. Tab Visibility 👀
To be honest, a lot of what I say is based on assumptions, so take that for what it’s worth. This is all based on my experiences with using Glide for the past couple of years.
Correct and correct! That linked thread is geeky-hilarious
My worries come from all the security warnings in this Glide instructional:
Row owners will def. keep users from seeing other users’ onboarding info, but ALL users have access to the Directory which is a separate sheet listing a particular group of people - it’s a list of profiles incl. names/phone numbers/email addresses - so on the VERY off chance that a user started harassing people in some manner I wanted a way to “ban” them from within the app - even tho according to Glide my ban method is rather weak. Part of it is also me wanting to alleviate any privacy concerns that could be raised by people listed on the directory sheet. Maybe misuse won’t be a concern, but I want to be prepared with an answer of “I already thought of that and I have a way to address it if it happens” (Or I’m just wayyy overthinking this) Members do also have a boolean in their profiles to turn off their listing…
Yeah, I’m not entirely sure. Maybe hiding tabs would be enough, but based on what I’m seeing, the data is loading regardless if the tab is visible or not. Those are some technicalities that Glide would have to answer to be totally sure. Your case hits some grey areas that I’m just not sure what the best approach is.
