Which Tableau user role has the ability to publish data sources and create new projects but cannot manage site settings?
Think about roles that allow content creation but not full administrative control.
The Publisher role can publish data sources and create projects but does not have rights to manage site settings, which is reserved for Site Administrators.
You want a user to edit existing dashboards but not delete them or change permissions. Which permission setting should you assign?
Focus on enabling editing but restricting deletion and permission changes.
Allowing 'Edit' and 'View' lets the user modify dashboards without deleting or changing permissions, which are denied.
In Tableau, if a user belongs to two groups with conflicting permissions on a project (one group allows 'View', the other denies it), what is the effective permission for the user?
Consider Tableau's permission precedence rules.
In Tableau, deny permissions take precedence over allow permissions, so the user is denied 'View' permission.
A user reports they cannot access a published dashboard despite being assigned the 'Interactor' role. Which of the following is the most likely cause?
Think about permission conflicts at the content level.
Even with the correct role, explicit deny permissions on the dashboard or group level will block access.
You need to create a Tableau dashboard that shows user roles and their effective permissions across multiple projects. Which visualization approach best communicates this information clearly?
Consider clarity and ease of comparing permissions across users and projects.
A matrix with color-coded cells allows quick scanning of which users have which permissions on each project, making it the clearest choice.