A secured column on a form shown to users without the grant

Form layout includes a field-level-security secured column.

Same problem on a form: users without the grant see a blank control that reads as broken rather than protected. Enforced server-side, so posture and UX, not exfiltration.

Same approach as views, against formxml instead. Grep the exported customizations.xml for each secured column's logical name and note which forms place it.

Remove the secured column from forms shown to audiences that lack the grant, or scope a form variant to those who have it.

These mappings are indicative. Pathix detects a condition relevant to a control. It does not certify your compliance, and a finding is not an audit opinion. You stay responsible for your control environment.

• A field-secured value copied into an unsecured column
• A secured column sitting in a default view
• Field-level security enabled with no profile granting access