Granting Query-only access to a specific presentation object (via Presentation Objects by Navigator) still lets users perform actions like adding new records on that screen — is this expected, and is there a way to actually lock it down to true read-only?

All FAQ questions / Security and access

Answer

This is worth checking separately from the UI-level Query grant: also review whether the user's permission set is granting database-object-level access (Insert/Update/Delete rights on the underlying API/table objects for that Logical Unit) — because even with the presentation object itself correctly set to Query-only, a broader database-object grant on the same LU can independently allow write actions regardless of what the screen-level Query setting suggests. Genuinely locking a screen down to read-only requires both layers (the presentation object grant and the underlying database object grants) to be restricted consistently, not just the presentation object grant alone.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Security and access questions