How to enforce staff-only edits on author-owned feedback rows?

Ask for Help
1

Hi everyone,

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:

  1. If an author can read their own row, what prevents them from modifying its status or staff reply through requests outside the visible UI?

  2. Are conditional add/edit/delete permissions enforced on the server, or only in the interface?

  3. If field-level write restrictions are unavailable, what supported architecture provides author-readable but staff-writable replies and status?

  4. 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.

Thank you!