some of the rep wantes to see their territory data on Pulse metrics.
Is it possible to do this on Tableau Pulse ?
or is their any capability of pulse we can achieve.
can you share a scenario or solution if I can achieve this?
#Tableau Desktop & Web Authoring #Tableau Pulse
Hi Himshikha - yes, this is doable, but the key thing is that you don't set up RLS 'in Pulse' itself - Pulse metrics inherit the row-level security of the published data source they're built on. So you implement RLS on the underlying data source, then build the Pulse metric on it, and each rep automatically sees only their territory's numbers (including in their Pulse insights and email digests).
Two ways to implement the RLS on the source:
1) Virtual Connection + Data Policy (the modern, recommended way). In Tableau Cloud, create a Virtual Connection to your data and add a Data Policy that filters rows by the logged-in user - typically by joining to an entitlement table (a user-to-territory mapping) and matching on USERNAME(). Because the policy lives on the virtual connection, it's enforced everywhere that connection is used - Pulse included - and you maintain it in one place.
2) Data source filter / user filter (simpler, classic). On the published data source, add a calculated field like [Territory Owner] = USERNAME() (or join to an entitlement table keyed on USERNAME()/USERUSERNAME()) and apply it as a data source filter, then publish. Pulse metrics built on that source inherit the filter.
End-to-end scenario: build and maintain a user-to-territory entitlement table, apply RLS via option 1 or 2 on the data source, create the Pulse metric on that secured source, and then each rep who follows the metric sees only their territory's value, trend, and insights.
Two gotchas: make sure the Tableau user identity actually maps to your territory field (via USERNAME()/USERUSERNAME() or a group), and test it by previewing as a specific user (the user-filter dialog lets you confirm what each user sees) before rolling it out.
Hope that helps!
