A Salesforce administrator uses Lightning App Builder to migrate an Opportunity record page to Dynamic Forms. To protect sensitive financial information, the administrator sets a component visibility rule on the Annual Revenue field so that it only displays on the page when the viewing user has the Custom Finance profile. Which statement accurately describes the effect of this configuration on users with other profiles?
- Users without the Custom Finance profile can still view the field data in reports, list views, and API queries if Field-Level Security allows access.Answer
- BUsers without the Custom Finance profile are automatically restricted from viewing the field data across all reports, dashboards, and API queries.
- CUsers without the Custom Finance profile will be prompted to select an authorized record type to view the hidden field on the record page.
- DThe field data is hidden in reports and list views but remains accessible to all users through API integrations.
Answer
Users without the Custom Finance profile can still view the field data in reports, list views, and API queries if Field-Level Security allows access.
Lightning App Builder component visibility filters control whether a component or field section is rendered visually on a specific Lightning Record Page. They do not alter object-level permissions or Field-Level Security (FLS). If FLS grants read access to a user, that user can still access the field's data through reports, list views, global search, and API integrations.
Step-by-Step Solution
Key Concept
Dynamic Forms Component Visibility vs. Field-Level Security