Is it the case that the boolean columns won’t work on a tab with row owners? I was trying to do a workaround accepting terms and conditions, but my users are row owners. The boolean works when row owners are off but won’t work when on. Just wondering if this was the case or if I was doing something wrong
I assume you’re using a normal Sheet column for the boolean?
I used a Boolean, should I use a regular text and show true or false?
1 Like
No that won’t change anything. Can you clarify what doesn’t work with the way you’re doing it now?
So as said, I wanna do a workaround for accepting privacy policy.
Situation:
App is public with the option to sign in. Before sign in user has to accept T&C otherwise the button will show a message, if accepted, then sign in. My users tap has row owners enabled, I add the checkbox button but doesn’t allow me to click, but if I disable row owners it does. Of course the checkbox would be user specific. Now, the question is, doesn’t it work because it has row owners enabled? But also does it need to be user specific since it has row owners enabled? I think I may answered myself…but hey, here’s the response 
. Thanks anyway @ThinhDinh
I think the easier way is to use Glide’s native T&C option. Would it work?
I think the problem you are running into is that you don’t have a row for the checkbox to update due to Row Owners being enabled. If the screen is not attached to a row, then all entry components are greyed out and you can’t change them. Disabling Row Owners is allowing the screen to attach to the first row in the sheet so you can update the boolean. The problem is you need the user to sign in to get a row, but you don’t want the user to sign in until they agree to the conditions. What you need to do is have a separate sheet with a single row and without row owners. In that sheet, you only need a single user specific column to hold the boolean value and then show or hide the sign in button based on that boolean. The sign in will fill the normal user profile sheet.
5 Likes
That makes a lot of sense Jeff, thank you both for your help
2 Likes
Hi @Jeff_Hager, I am bupping into the same issue, and thank you for this solution.
However, I have a question: as an admin of the app, aren’t we able to modify the boolean value of any users ourselves? If yes, what is the “legal value” of the T&C?
I hope my question is clear…
Thank you!
You would need to view the App in the builder as a specific user, but yes.
I don’t know, but how else would you do it?
A Glide App builder can change any value in any table as any user. That’s just the way Glide is.
2 Likes
No clue 
this is why I asked!
I’m not a lawyer, so I won’t get into legalities of what can or cannot hold up in court. But, from my experience as a developer at a company that deals with government related programs, and a lot of PII…from a legal perspective, there are COI forms, NDA forms, and various regulatory training that that I need to fill out and comply with each year. The company is also subject to various SOC audits every year by independent auditors to make sure procedures are followed. It’s my duty as a developer to follow procedure and do everything in my power to protect user data, even though I have access to much of that data and have the ability to manipulate it. I can be held legally responsible because I signed the paperwork saying that I would be.
In my opinion, if a developer cannot be trusted to have access to such data, then they shouldn’t be allowed access to the data, and possibly not be a developer in the first place.
It’s up to you and your legal counsel to determine what’s compliant or not. As far as the above scenario is concerned…and especially if you use Glide’s build in user agreement functionality on the sign in screen…if a user was able to sign in, then the T&C box was checked at some point to allow them access into the app. If that is not sufficient enough for your use case, then maybe you need to obtain signed paper documents that can be filed away in safe storage. Or enlist the services an independent third party to handle and enforce agreements. You as a developer have the burden of proof that a user agreed to terms, and need to provide that proof if there is ever a dispute.
3 Likes