A secured column sitting in a default view

Default view exposes a field-level-security secured column.

A secured column sits in the default view, so its header shows to everyone and rows without a grant render blank. Dataverse still enforces access, so this is a posture and UX gap, not a leak.

For each secured column, search the FetchXML of the table's default views for its logical name. Exporting the solution and grepping customizations.xml is faster than clicking through the view designer.

Remove the secured column from the default view; make a separate view for the audience that has the grant.

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 on a form shown to users without the grant
• Field-level security enabled with no profile granting access