When securing data in FlexCards, which approach is recommended?

When securing data in FlexCards, which approach is recommended?

• A. Expose all fields by default to ensure transparency.
• B. Use DataRaptor data masking only.
• C. Rely on Salesforce Field-Level Security and ensure FlexCard data sources honor permissions; avoid exposing restricted fields.
• D. Hard-code user permissions in the card logic.

Answer: (C)

Relying on Salesforce Field-Level Security and ensuring FlexCard data sources honor those permissions is the recommended approach because it enforces access control at the data source and across the UI consistently. By using FLS, you control who can see which fields at the Salesforce layer, and when the FlexCard’s data sources (such as DataRaptor or Salesforce connectors) respect those permissions, restricted fields will not be retrieved or displayed for users who aren’t allowed to view them. This centralizes security, reduces the risk of accidental exposure, and scales with changes in user roles and permissions. Relying on masking alone can hide values after retrieval but doesn’t prevent access to the data in transit or guarantee that restricted fields are not fetched or used by the card logic. Hard-coding permissions in the card logic is brittle and defeats the purpose of centralized security management. Exposing all fields by default is unsafe because it bypasses the established permission model.

Relying on Salesforce Field-Level Security and ensuring FlexCard data sources honor those permissions is the recommended approach because it enforces access control at the data source and across the UI consistently. By using FLS, you control who can see which fields at the Salesforce layer, and when the FlexCard’s data sources (such as DataRaptor or Salesforce connectors) respect those permissions, restricted fields will not be retrieved or displayed for users who aren’t allowed to view them. This centralizes security, reduces the risk of accidental exposure, and scales with changes in user roles and permissions.

Relying on masking alone can hide values after retrieval but doesn’t prevent access to the data in transit or guarantee that restricted fields are not fetched or used by the card logic. Hard-coding permissions in the card logic is brittle and defeats the purpose of centralized security management. Exposing all fields by default is unsafe because it bypasses the established permission model.