- What is "GDPR"?
- Why does the team consider it an issue?
That feature -- which is actually nice to have -- is built-in to Tableau Server. It would require custom work to disable it, would not be supported by Tableau, and could quite possibly change in a later release and thus invalidating the custom work used to hide it.
Sorry for not clarifying on this
GDPR is the General Data Protection Regulation enforced by the European Union. It is quite restricitve and sanctions are quite high.
It aims to give employees/people control over their personal data and its usage.
The views of who has viewed the report already would potentially infringe this regulation and therefore we would like to check if there is a way on how we can disable this.
Hope this explains the reasoning behind it.
Hmmm. Many entities (including the company that I work at) are having to deal with GDPR for consumers. However, for my company, we don't really see the "who has seen what view" an infringement. It's really just a usage tracking mechanism of what dashboards have been leveraged by people within our on-premise Tableau Server deployment. And if these people are all employees that have signed a consent agreement, even more so not an infringement.
If you really want to disable auditing altogether, or limit history, there may be a few tabadmin config settings you can adjust. Look for "audit" within this link. tabadmin configuration options
Yeah, I have to agree with Jeff on this. People shouldn't get too crazy about this, I'd argue reasonability within the context of the business.
Okay, thank you all!
I understood that there is no way to completely diable this option, but that this might not be relevant for GDPR.
As a sidenode, do you know if Tableau Server can sen encrypted mails?
You could disable the workbook template. With a stopped Dev server browse to the vizql.war file. Crack it open with your favorite unzipper:
Then browse to the workbook and rename it.
I've changed mine to viewOFF.ftl.
And here is the error message I get when trying to access the "Who Has Seen This View."
This is completely unsupported and frowned upon. Please test appropriately. Oh and everything that Toby mentions in his first comment.
Also, the data is still being collected so anyone with credentials to the postgres DB could still have access to it.