4 Replies Latest reply on Oct 8, 2018 9:10 PM by 玟卉 賴

    Hidden for user dimension

    玟卉 賴

      Hello everyone

       

      I recently encountered a problem.

      When different accounts are edited in tableau online, all the dimensions of the data source will be displayed.

      For example, the dimension in my data source "Total Table":

      Dimention:1. Salesperson 2. Sales date 3. Purchaser 4. Shipment date 5. Product

      Value:1. Purchase amount 2. Discount amount 3. Actual payment amount,all dimensions and values will appear.

      However, this workbook must also be viewed for different accounts.

      The salesperson only wants to display the salesperson, sales date, and purchase amount.

      The PM only wants to display the purchaser, product, purchase amount, discount amount, and actual payment amount. What should I do?

        • 2. Re: Hidden for user dimension
          suman kumar

          Hi,

           

           

          Restrict Data Access with User Filters and Row Level Security

          Restrict Access at the Data Row Level

          When you share workbooks with others by publishing them to Tableau Server or Online, by default, all users who have access to the workbooks can see all of the data shown in the views. You can override this behavior by applying a type of filter that allows you to specify which data “rows” any given person signed in to the server can see in the view.

          How user-based filtering works

          Suppose you created a quarterly sales report for a set of products over several years, in different geographic regions.

          When you publish this report, you want to allow each regional manager to see only the data relevant to his or her region. Rather than creating a separate view for each manager, you can apply a user filter that restricts access to the data based on users’ characteristics, such as their role.

          Restricting access to data in this way is referred to as row-level security (RLS). Tableau offers the following approaches to row-level security:

          • Create a user filter and map users to values manually.This method is convenient but high maintenance, and security can be tentative. It must be done per-workbook, and you must update the filter and republish as your user base changes.
          • Create a dynamic filter using a security field in the data.Using this method, you create a calculated field that automates the process of mapping users to data values. This method requires that the underlying data include the security information you want to use for filtering.The most common way to do this is to use a reference (or “look-up”) table that contains this information. For example, if you want to filter a view so that only managers can see it, the underlying data must include user names and specify each user’s role.Because filtering is defined at the data level and automated by the calculated field, this method is more secure than mapping users to data values manually.

          Adding user filters to data sources

          The two approaches in the previous section describe ways to add filters to data embedded in workbooks. If multiple workbooks connect to the same data, instead of wrangling filters on each workbook, you can filter the data source, and then connect the workbooks to the data source after you publish it.Workbooks that connect to your filtered data source expose only the data the user signed in to the server is allowed to see. In addition, all connected workbooks show data refreshes as they occur.

          Extracts vs. live connections with user filters

          The related topic describes how to publish a live connection with user filters. Publishing extracts with user filters has its own complications around row duplication and performance. These are not addressed here.However, we can direct you a comprehensive discussion about row level security with extracts, on a blog maintained by a Tableau Sales Consultant who has extensive experience with this area. See the following two posts:

           

          Best

          Suman

          • 3. Re: Hidden for user dimension
            玟卉 賴

            Hello Suman

            Thanks for your response. The solution you suggest hides the data within the column, but still exposes the column to the User. Ideally, I wouldn't want to show the column itself to the User.

            • 4. Re: Hidden for user dimension
              玟卉 賴

              Hello sankar

              Thanks for your response. For column level security I can vote in idea section.