Under what conditions can Salesforce user tokens (user.id) be used as filters?

Salesforce user tokens (user.id) can be utilized as filters specifically when the data source supports user and role filtering. This condition is essential because for user tokens to function effectively, the underlying data must have the capability of differentiation based on user identity and roles. This means that the data source must be set up to allow for dynamic filtering based on who the user is, leveraging their specific user.id to tailor the data they see according to their role, permissions, or other user-specific attributes.

For instance, when a report or dashboard is created and user tokens are integrated, they can ensure that each user can only access the data that is relevant to their role in the organization. By using user tokens within a supportive data source, the system can apply the correct filters automatically, delivering a personalized experience in visualizations where users see only the data pertinent to them.

In contrast, other options do not meet the criteria needed for the effective application of user tokens. Visualizations for unlogged users cannot use user tokens since there is no user identity to reference. Connections to social media do not typically involve user tokens for filtering data, and referencing static data does not require dynamic filtering based on user identity, which is the essence of utilizing user tokens effectively.