Overview of Project permissions?

Overview of Project permissions


Workbooks and data sources are always published to projects in Tableau Server. Use projects to:
Keep related content together. You might create projects based on audience (e.g. finance), role (e.g. administrators), or function (e.g. production versus sandbox).
Manage access to project content by different groups of users. This could mean granting different permissions to different groups for the same project. Or it could mean creating multiple projects that some team members can access and others cannot.
Set default permissions for all content in a project. Set the default permissions so that workbooks and data sources published to the project start with those permissions. We’ll show this in the walkthrough later.


Overview of Project permissions
About users and groups
Unless you deployed Tableau Server to support Guest users, every person who wants to publish content to or view it from the server must sign in as a Tableau user. And each user must have permissions to work with content.
To manage user permissions, we strongly recommend that you organize users into groups. You can then set permissions at the group level to apply a set of capabilities to all users in the group.
A recommended practice is to create groups based on functional categories—Content Managers, Content Viewers, Data Managers, or even combine functional category with department; something like Marketing Viewers and Marketing Publishers. The point is to create groups whose members need to work with content in the same way. A user can belong to multiple groups as well, meaning they get the permissions from all of those groups.

Leave a Reply

Your email address will not be published. Required fields are marked *