I know enabling Glide for sensitive data creates a bunch of issues. But this may be a good step in the right direction.
Give us an “obscure data” option in the editor.
Like the “user-specific” column. If we click it, any data in that column gets obscured to us in the data editor like #–obscured–#, or something. We can’t see it. But the data still shows as needed on the front end. Very similar to how it does with user-specific functionality.
I know it’s not perfect for HIPAA etc. But I’m also willing to bet almost every builder on here has prohibited or sensitive data on their apps (addresses, phone, etc). At least this gives a layer of protection to us, in an easy to build manner for Glide.
We can already obscure the data in the data editor by editing the column and clicking protected.
I’m not sure this part is possible… if you protect the column in the editor it won’t show on front end because the data is never downloaded in the first place
1 Like
Yeah, but that’s only available with external data sources.
3 Likes
Yes! Like this!
Except, like @Darren_Murphy says, enable this for Glide tables, not just gSheets. All it needs to do is black out the data to us builders. So only the user can retrieve it in their apps.
It could also do a partial obscure to us on the front end to still allow proper testing (like credit cards do, obscuring the middle numbers).
Not only here in Glide. It would be nice for instance if the data in CRMs were obscured for the users of the CRM. I don’t find it normal that just about anyone in a company who has access to a CRM has access in one way or other to customer data. Marketers could do their campaigns without actually knowing the names and email addresses of people, sales people could make their calls by knowing only the information they need and nothing more.
Likewise, developers in Glide don’t really need to know private information in detail to build an app.
Voted.
1 Like