In Salesforce, when an administrator hides a field using Field Level Security (FLS) for certain profile types, some users may still be able to view that field in reports. Field Level Security (FLS) controls field visibility across Salesforce, including reports, list views, search results, and API access.
This article describes the most common reasons a field hidden through FLS may still appear in reports and provides steps to identify and resolve the issue.
This article explains three common scenarios in Salesforce where a field that is expected to be hidden still appears in reports, and how to correct each situation.
If a field is hidden only on a page layout, users may still access it through reports, search results, list views, and the API. Page layout visibility does not restrict field access; only Field Level Security (FLS) controls access to the field itself.
To verify and correct this:
Review the field's Field Level Security settings.
Check whether the field is marked as Hidden for the affected profile.
Hover over Hidden to determine whether the field is hidden because of the page layout or because of Field Level Security.
If the field is hidden only by the page layout, click Hidden for the appropriate profile and clear the Visible checkbox to enforce Field Level Security restrictions.
In some cases, the field displayed in the report may be a renamed version of a different field.
Review the following possibilities:
If the report was created using a Custom Report Type, the field may have been renamed through the Edit Layout section.
For organizations using Translation Workbench, review whether a translated label exists for the user's language on a field within the same object.
For Managed Packages, verify whether the field label has been overridden through package translations or customization settings.
A Permission Set can grant field visibility beyond the access provided through a user's profile.
To troubleshoot:
Review the affected user's assigned Permission Sets.
Check the field permissions granted by each Permission Set.
Confirm whether the field has been explicitly granted visibility through a Permission Set assignment.
Remove or modify the Permission Set permission if the field should remain hidden.
Set Field Permissions in Permission Sets and Profiles
Design the Field Layout for Reports Created From Your Custom Report Type
Manage Your Translations
Translate Metadata Labels
Override Translations in Second-Generation Managed Packages and Unlocked Packages
000387842

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.