4 Replies Latest reply on May 3, 2017 3:51 PM by Kim Wayman

    Desktop only License and sharing information?

    Peter Graham

      Hello Folks,

      I'm hoping to hear back from folks on best practices for sharing work products with executives and other staff members, when there may only be a handful of desktop users? PDF? Tableau Reader? Does the interactivity/functionality work? Or any other tips and tricks.


      Thank you,


        • 1. Re: Desktop only License and sharing information?
          Jim Dehner

          Hi Peter

          It really depends on what you want your user to be able to do


          For the exec level if you want them to see/read only then PDF is a good way to give them a static report

          On the other hand you want to let your user to drill through the viz along the lines of the filters and actions you set up - then Reader will let them get deeper into the analysis - but they will not be able to change calculations or the data itself - that may be an advantage


          Hope that helps


          • 2. Re: Desktop only License and sharing information?
            Chadd Bennett

            Hi Peter, great question!

            As the Student Achievement Council a small agency with just one active Desktop license (and developer) and currently without Tableau Server we've tried a number of options. With our current setup we only load preaggregated or non-confidential data (cat 1 and 2), and the most successful for us, depending on audience need/use have been:

            • When interactivity is most important, "Hidden" Tableau Public pages with visibility and workbook downloads off. For internal audiences, we embed it in our Confluence wiki/intranet (see screenshot), so that staff can easily find it again and we can control access to internal groups; for (targeted) external stakeholders we can publish as orphan pages on our main site.
            • When P's* are most important PDF exports have worked OK, but you lose tooltips and interactivity...*portability, printing, providing feedback, or porting to Illustrator/InDesign.
            • We opted against Tableau Reader since frequent-enough version changes were burdensome on IT resources.



            • Embed codes are based on the sheet name, and will change/break if you adjust the sheet name. I try to have a generic "overview" slide that will not likely be renamed.
            • Having a separate Tableau Public account is an option for additional isolation of external/internal data...which just highlights the governance issues of using Tableau Public!


            I'm also curious what others are doing!



            Image 025.png

            • 3. Re: Desktop only License and sharing information?
              Steven Suskin

              We're using Tableau reader for the execs and find it works well.  Yes, it is sort of annoying to have to upgrade the reader every time the desktop is upgraded.  But, we've minimized the disruption caused by that issue by choosing to be selective about our upgrades; i.e. only upgrading when there is functionality or bugs that are relevant to our use of the tools.  We've found that you can also publish the reader files to SharePoint and open then from the site which allows us to publish and maintain our data files in one location for the execs.  Our feeling is that the value of Tableau is in the interactivity of the product. While you can publish to .pdf, the value of the original content is greatly diminished.

              • 4. Re: Desktop only License and sharing information?
                Kim Wayman

                Hi,  We asked our IT to push out Tableau Reader to all supervisors and above and we upgrade accordingly.