An administrator adds a custom component to an Account Record Page and applies component visibility filters so that it appears only for users with the Executive profile. A colleague suggests that this setting will also prevent non-executive users from seeing the underlying data in custom reports. Which statement accurately describes the security behavior of Lightning App Builder component visibility filters?
- Component visibility filters only control whether the component renders on the Lightning page; they do not restrict data access in reports, list views, or API calls.Answer
- BComponent visibility filters automatically update Field-Level Security to prevent user access via reports and APIs whenever the filter criteria are not met.
- CComponent visibility filters update record type picklist assignments to restrict field access on related page layouts.
- DComponent visibility filters override Organization-Wide Defaults to restrict object-level read permissions for profiles not specified in the filter.
Answer
Component visibility filters only control whether the component renders on the Lightning page; they do not restrict data access in reports, list views, or API calls.
Component visibility rules in Lightning App Builder are client-side UI display criteria. They control whether a component is visible on the screen but do not enforce security or restrict access to data accessed through reports, list views, or external APIs.
Step-by-Step Solution
Key Concept
Lightning App Builder Component Visibility vs. Data Security