![]() ***License would have to be adequate to the highest Role One might be a Viewer on one site and a Site Administrator Creator on another.*** In short: Make sure that the capability you want to grant to a user is aligned with his/her license and site role. Please mind that unlike the license, which is assigned one per user, Site Role is assigned (like the name suggests) per site. **if a Creator license is available on the Server, Server Administrator role will take it automatically We will go a step further and add those site roles to our table, along with a few additional capabilities that depend on the Site Role only: Depending on a user’s license, we may be limited to give him/her only certain roles. Site Roles and Their CapabilitiesĪs showed on the first image, the second level is site role. In short: If you are trying to assign any of the permissions to a user, make sure that his/her license allows that permission. ![]() However, from the Tableau Server point of view, the only difference is that Explorers cannot create data sources. In reality, there are two additional differences: Creator can use Tableau Desktop and Tableau Prep while Explorer cannot. It may seem counterintuitive that the only difference between the Explorer and Creator is the last part: creating data sources. You can check it as a server admin and make sure that the license is correct for the highest role. *Users can have different roles across the sites. That is the lowest level, and in many circumstances, changing this one may not change anything if any of the above prohibits it. Content permission can be applied to multiple different object types. However, an Explorer role can be explicitly denied editing or any other action for specific content.ģ. For example, a Viewer role cannot edit content even if explicitly given a permission. ![]() The site role (one per site) can be chosen from seven different roles, and it limits what a user can do with the content. Tip: it is a waste and such a user should have a lower-level license.*Ģ. A user that has a Viewer license cannot be an administrator however, one with a Creator license can be just a Viewer. ![]() Tableau explains this part the best by creating a simple hierarchy. It all depends on the correct combination of the permissions. There are several levels of permissions that come in a hierarchy you should understand before you decide to start giving all your users and groups different privileges. How to Create the Tableau Permission Setup In short: you have more detailed control. We can set those up for the following: Project, Workbooks, Data Sources, Data Roles, Flows and Metrics. Now that we have more intuitive permission settings, we can select groups or users and apply template or custom permissions to each individually. ![]() In short: this is a new possibility to delegate: That gives us a possibility to lock some parts of a project and set other parts to Customizable, which allows the content owners (we will discuss those later) to change them. We can now separately control projects and their content. Let us quickly take a look at those new features below. This article will describe those and explain how to handle all the new options without getting lost. The main point to know here is: Are we running a pre- or post-2020.1 Tableau Server? In 2020.1, Tableau released important changes to the permissions. We should start from quickly discussing the changes to the permissions. So let’s examine this common topic and demystify the permissions. That is because there are several places where we can control the permissions, sometimes even using settings that may not seem immediately obvious that influence the permissions. Making sense of Tableau permissions can be difficult without a solid guide and a consistent plan on how to execute them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |