We recommend it so that project owners can perform the full range of administrative tasks that you’ll be responsible for, including publishing content into your ‘production’ (official, verified data) folders.
You can publish to any server with your desktop license. You will likely be limited to publishing only to your unit’s Project.
No – inactive users are not taking up a license per se as we have server-level licensing. There is also no significant performance impact if a user walks away. Concurrent usage is active querying of data, which a user wouldn’t be doing if they are away from their desktop. We do not anticipate exceeding this limit, but will continue to monitor the usage and increase capacity if warranted.
The best options to control access to underlying data in the data source are outlined by use case.
If you want to control the permission for a specific workbook only (as opposed to the data source in general), set the restriction at the workbook level.
If the consumer has only the ‘Viewer’ role at the Site level, by default, they won’t be able to use the ‘Download Full Data’ option (though they will be able to download the summary data as presented in the visualization). Note that any fields used in the background will also be in the download.
If the consumer has the ‘Explorer’ role or higher at the Site level, by default, they are allowed to download full data. This can be turned off at the project or workbook level.
The Flagship Analytics site has various groups for senior leadership, deans, associate and assistant deans and department heads and chairs. These groups are maintained as changes are communicated. There are no groups maintained centrally on the Amherst Data Pond site; you need to provision people individually to your content.
All faculty and staff are automatically added to the Flagship Analytics site.
There are a large number of individuals on the Amherst Data Pond site, so you can look up anyone you may need to add. If you can’t find someone, please contact Tableau Support (tableau-support@it.umass.edu).
Not at this time. IT is exploring options for “guest” access.
The Project Leader can make content security as granular as you like in your project: at project level, at sub-project level, at workbook level. The dashboard creator can also control access to his/her dashboard.
Yes. We recommend this for cases where you want to segregate content within your main project.
No, we looked into it and it will not work for us. What we are doing instead is import new SPIRE roles.
Contact Tableau Support (tableau-support@it.umass.edu) if your School/College does not have a Project and you would like one. Academic Departments will be Sub-Projects of School/College Projects, so your Project Leader can create one for you.
Users log in individually, not at the group level, so yes, it is possible to see who is/has been logged in. The Tableau Support team has access to usage reporting.
At this time, we are directing you to online training resources, which are very good for learning the basics.
We are looking at products to help us store and present data dictionary-type information, but we would need data experts from all areas to work on this project.
Yes, we have a license key we can give you. Contact Heidi Dollard or Chelsea Reilly. However, this is not yet a mature product. Some of our Tableau users recommend Knime (free version) instead, which is a more mature, robust data prep workflow tool. Alteryx is another major competitor in this space but is very expensive.
Other users use Excel or MS Access for data prep.
Note: Tableau Prep is Tableau’s entry into data preparation software, which helps with the cleanup and preparation of data before you use that data as a data source for an analytics tool like Tableau.
HelioCampus controls the application of upgrades to our server, and they will apply upgrades 2-3 times a year. We will work on advance notice with Helio to their schedule and consider strategies to allow for testing before the upgrades are applied.