Guest access allows users that do not have an active account on Tableau to view dashoards/workbooks.
These users do not necessarily have to have an account (LDAP authenticated in your case).
These users are provided a shared link which they click and access the Tableau artifact.
Possible reasons could be:
- These users need to access just one dashboard among many.
- User limit set on a site .
we use guest access quite a bit.
Hope this helps
Thanks for the quick response!
does that mean that we don't need to have the user on an AD group for them to see the dashboard? And that we can't see who is looking using custom views?
At the moment everyone has to come in via AD group (one for interactors, and another for publishers). Then the permissions are set based on those AD groups, and row level security is either controlled at source, or using a separate datasource that is connected using a cross data-base join. In this case, would it make sense to have the guest access on? and does it do any harm?
You present a interesting challenge.
You would like to track Views usage for a User. In the case of a 'guest' user the usage metric is reported as under 'guest'.
Then you have a row level security. Firstly if you indeed have a 'guest' opening a Link to a view it won't render 'cause the 'guest' user is a local Tableau account on Tableau.
You could try the following:
(1) Have IT create a email@example.com account in AD, which I am sure they will resist.
(2) If (1) is possible the row level security you have in play would work for the guest access via the link.
(3) Using a separate datasource that defines your row level security ( am assuming you will have a user, access levels...etc in it) cross joined to the data set to be reported on, the final resulting data set would explode to as many users. Which is not efficient.
If the View does not need any row level security you could always set permission for the View for the 'guest' user by editing the permissions .
Given that we can't share any content outside our firewall, and that we want to have the content restricted for everthing (apart from content in one site), then there really isn't a use case for us to use guest access. Is that right?
We have 1 site that's available to everyone - so in that case, we should enable guest access? but for all others, just switch it off?