I’m building a feedback feature using Glide Tables and signed-in users:
Users submit suggestions and see only their own.
Staff can see all suggestions and update their status and reply.
Authors must not be able to change staff-only fields or assign themselves staff access.
The proposed setup is one suggestions table with two Row Owner columns: author email and staff role.
My question concerns server-side write authorization, rather than which rows users can download:
If an author can read their own row, what prevents them from modifying its status or staff reply through requests outside the visible UI?
Are conditional add/edit/delete permissions enforced on the server, or only in the interface?
If field-level write restrictions are unavailable, what supported architecture provides author-readable but staff-writable replies and status?
How should authorship, ownership and staff roles be assigned and protected?
I’m seeking configuration guidance, not reporting a confirmed vulnerability. Documentation or clarification from the Glide team would be appreciated, including any plan limitations.
To the best of my knowledge, I don’t believe there are any protections in place to prevent someone from intercepting an API call for a row they are an owner of. Can’t confirm that 100% but Glide does stress that filters and visibility conditions are not security features, so that implies to me that it’s possible.
Conditional permissions are enforced only on the interface.
Don’t have an any suggestions. There are no column level permissions that are available to us. The only exception is the role column in the user table, which can only be changed server side.
I don’t have a good answer for enforcing column level permissions and roles. I personally don’t think it exists, but I’ve also never heard of anybody bypassing and injecting data into an API call. In any case, I always operate on the assumption that it’s possible with enough knowledge on how to do it.
Based on the assumed limitations, I can’t think of a good workaround that would guarantee someone wouldn’t be able to bypass the built in controls limiting them from changing data on a row they own. If they have access to the row, I believe they can bypass any write capabilities regardless of any visibility conditions on the controls. Maybe I’m wrong, but this question has come up before and nobody from Glide has ever confirmed or denied the possibility. You may be better off contacting Glide support directly to get clarification.