1. Tableau Environment and User Roles Re: Amherst Data Pond
3 Web User Roles
‘VIEWER’ :
View visualizations, dashboards, storyboards
Interact with data
Download summary data $
Data Sources (Examples)
Web User - Consumer
DATA SERVER
Connections to Data Sources
Semantic metadata modeling
Interactive Dashboards
‘EXPLORER’ – all ‘Viewer’ tasks plus:
Connect to published data sources
Ad hoc queries (no save)
Download full data
Can manage projects
Verify / certify data
Ad Hoc Data Discovery & Visualization
Interact
Web User - Publisher
Web Edit* $
DATA PREP CONDUCTOR
Run data prep workflows
‘EXPLORER (CAN PUBLISH)’ – all ‘Explorer’ tasks plus limited publishing:
Edit & save existing workbooks (Web Edit)
Copy/save data connections from existing workbooks
Interact & Publish
TABLEAU SERVER
Interact & Publish
Desktop User – Publish
CREATOR: all Explorer plus:
Create & publish new vizzes, dashboards, data sources
Export data
Prepare data
Publish, schedule flows
*Web Edit has only a small subset of creation and publishing features compared to Tableau Desktop. E.g. Data sources limited to Excel or text files.
Desktop License:
For power users/ creators
Richest feature set
Connect to broadest range of data sources
Tableau
Data Prep
Tableau
Desktop $
$: Requires additional license fees
$ No additional license fees

2. Tableau Security - Use of Sites and Projects
A ‘Site’ has its own security, users, projects, and data content - no sharing of these across sites.
PROJECTS
Each Site can have multiple ‘Projects’ to group content as desired
Each project can contain one or more nested projects as needed
CONTENT
Workbooks: where you build analyses, visualizations, dashboards
Data Sources: connections to data. Workbooks use one or more Data Sources
TABLEAU SERVER
Data Pond Site
Flagship Site
(HelioCampus)
Project A
Nested project 1
Enrollments Dashboards
Financial Aid Dashboards
Workbook 1
Data Source 1
Nested project 2
Student Success Dashboards
Admissions Dashboards
Workbook 2
Data Source 2
Faculty Dashboards
Project B
Nested project 1
Workbook 2
Data Source 2

3. Projects – Management and Administration
PROJECT MANAGEMENT
Propose that IT creates one top-level project per School, College, VC Dept.
A Project Leader (or Leaders) will need to be appointed for each Project to perform project administration (see box.)
Sub-projects can be added within each project to further organize content as needed (e.g. departments within a College.)
AMHERST DATA POND SITE
PROJECT
School / College 1
PROJECT
School / College 2
PROJECT
School / College 3
PROJECT
VC DEPT 1
PROJECT
VC DEPT 2
Production
Production
Production
Production
Production
Sandbox
Sandbox
Sandbox
Sandbox
Sandbox
CHANGE MANAGEMENT - RECOMMENDATIONS
Recommendation is for each project to identify ‘production’ versus ‘sandbox’ sub-projects to distinguish unverified vs. verified analytics.
Production projects: Use to share verified, publishable analytics
Sandbox projects: Suggest to be used for cases like
Rapid prototyping – trying out new analytics and concepts
Data Exploration: Exploring unverified data sets or data sources
When Sandbox content is ready to share with a broader audience, publish into the Production sub-project.
PROJECT LEAD - ROLE
Lead(s) appointed by School / College / VC Dept
Creates sub-projects as needed
Assign users to project & sub-projects
Oversee and propose Quality Control, Change Control and Data Security practices in their projects

4. Proposed Security Configuration for Amherst Data Pond Nested Projects; Groups aligned with Projects / Nested projects; Consumers and Creators
AMHERST DATA POND SITE
Examples
Project: IT
Sub-projects
Enterprise Systems
Networks
Sandbox projects for each
Project: R&E IT
R&E
Nested project 1
Ent. Systems
Vice Chancellors & Deans
Workbook 1
Data Source 1
Workbook 1
Data Source 1
Nested project 2
Ent. Systems Sandbox
Academic Department Heads
Workbook 2
Data Source 2
Workbook 1
Data Source 1
Nested project 1 - Sandbox
Networks
Workbook 2
Data Source 2
Workbook 1
Data Source 1
Networks
Sandbox
Workbook 2
Data Source 2