1 of 1 people found this helpful
Hi Vivek, I would start by looking into creating datasources with embedded credentials:
If you are using SQL Server, impersonation might be an option: Impersonate with Embedded SQL Credentials - Tableau
Once you've created your datasources, you can use row level security to provide control over which users can see which data: Restrict Data Access with User Filters and Row Level Security - Tableau
Thanks a lot Jeff for your reply. I think I have understood your solution. Let me say it back to you:
So basically I will get myself the database access first (DBA does not have any problem in giving me full read access)=>build dashboard along with row level security and while publishing it onto server either follow impersonation or embedded password.
Kindly clarify if my understanding is correct.
Also what would happen if my credentials are changed? As per IT policy I would probably be changing my windows password monthly.
Or instead of me getting access should a new user be created for accessing this different database which would have same password forever?
Hi Vivek, your explanation sounds correct. Start with the embedded password approach. Impersonation or row level security may not be necessary -- that will depend on your requirements.
If your organization has a password rotation policy, then creating a service account with a fixed password is a good solution.
Thanks Jeff. Let me try the embedded password approach. I don't know why I
remember long ago when I tried to embed password for a SQL data-source, the
workbook, when published, was still trying to use the service account
instead of the one that I embedded.
Vivek - What was your solution?