2 of 2 people found this helpful
Right now, you can't publish a single workbook (and data source) to multiple sites on Tableau Server, and have the workbook stay in sync across all sites. The workbook would be treated as an individual workbook on each site of Tableau Server, and would have to be individually published to, and updated on, each site. I'd recommend posting this idea to our Ideas forum:
A way to accomplish what you described might be to use Project, Workbook, and View permissions to deny the users access to Projects, Workbooks, or Views that they should not see. The single workbook could have changes made to it, and all users would see the changes, without needing to republish the workbook on all ten sites.
1 of 1 people found this helpful
why do you have so many sites? do you basically have one site for each client so that they can only see their data? there may be a more slicker way of handling this if this is what you're trying to do.
Yes Jeff, I only want each client to see only their data, using one workbook.
Any thoughts how to accomplish this?
4 of 4 people found this helpful
We do this all the time as we have clients that can only see their data. Here's the method of data blending, let me know if you need any further clarity:
1. Primary dataset with client performance data (we call it Performance Topline IO). Within here is company id.
2. Secondary dataset that is keyed on logged in userid and one row per company that the id can see. There is an extra field in ours called "company name" but this really isn't needed because it's in the primary.
3. A calculated field in the secondary dataset called user filter. "IIF(CONTAINS(LOWER([Username]), LOWER(username())),1,0)". This creates a flag based on the logged in userid (username) compared with the field in the secondary datasource (Username).
4. A data blend within the workbook based on company_id. Make sure that the orangle link shows up and is fully linked. We know that data blending can be performance heavy, however if the secondary dataset is small in size, then it's not really so heavy.
5. Apply the User Filter of 1
Two more things to note:
1. If you want company name to be a quick filter, then it will show the entire list (because of order of operations). This is ok for our internal account managers, however for our clients, they don't get a dropdown. Rather they have a portal where they login and the security is placed up stream.
2. We did not use Tableau's built-in data security because it's based on AD groups which seems to rigid for handling client provisioning.
3. In our case the primary and secondary are both Tableau data extracts.
This is very helpful and thank you so much!
We will be meeting with our rep from Server this afternoon to assist us in publishing this workbook on Server.
please mark as helpful or correct.