Some context on how this works:
Our service users/application users (the bots that send the emails) do not run under the identity of the user who created the journey (RTM does not allow impersonation). They run under the service user identity. These service users cannot access fields that have Field Level Security (FLS), unless they are specifically added to the customer field security profile (aka group of users that can access the secured field).
In this case, we can only do one of two things:
1. Flip the FLS protection - Add the service users to the list of access groups for these FLS protected attributes – In this case, everyone in the system who can run journeys will be able to render values in these fields even if they themselves are not part of the FLS access groups. Once this is complete, we need to enable a feature flag that currently does not allow FLS enabled attributes for personalization.
2. Aggressively lock down who can publish journeys and through that, protect who will be able to see the data, as the person publishing the journey will have the option to review what’s happening prior to publishing. – You can enable this only for admins in your case.
