Does anyone know if this would work: So far all I've been able to find is that I can give separate projects permissions, so I could keep all of our QA'ed datasources in one project and only give these users connect permissions and then allow them to save permissions to a different project, which would at least keep all the datasources separate from each other. Does anyone know if this is accurate?
Thanks in advance.
2 of 2 people found this helpful
The scenario you described is how I manage all of my Tableau Server environments.
Most functional areas (Finance, Sales, Inventory, etc.) have their own projects for Workbooks, and datasources are typically not published to these projects. Power users have the ability to publish workbooks to these projects.
Datasources have their own projects, where most users only have connect permissions. A much smaller set of users have permissions to publish in the Datasources projects.
I don't have an automatic security-based solution for disallowing users to publish workbooks with embedded datasources. This can be solved by implementing a workflow for content creation in Tableau, where everything is reviewed and approved by an approver (designated admins or power users) before the objects are promoted to production. The approvers ensure all workbooks and datasources conform to the standard you have specified.
President & Chief Architect