How to validate server-side READ_ONLY write rejection for authenticated AppSheet users?

Hello AppSheet Community. We are testing a multi-user AppSheet application using synthetic data in an isolated environment. We use READ_ONLY table permissions, security filters and required sign-in. Is there an officially supported way to confirm that the AppSheet server rejects unauthorized Add, Update and Delete requests from authenticated read-only users, without modifying existing permissions? What server-level evidence (logs, response codes or other mechanisms) confirms rejection? Does enforcement also apply to related-record operations? What validation procedure is recommended if the interface offers no write controls? We seek general technical guidance only. Thank you.

The audit log may surface the rejection. Try performing an unauthorized operation and check the log.

READ-ONLY table permissions assigned WHERE?

In an AppSheet, if you are referring to setting tables in the app as READ-ONLY, the app itself rejects the ability of Add, Update and Delete. These buttons are simply not shown to ANY user and therefore the actions are PREVENTED. No rejection necessary!!