User permissions and roles in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Tableau User Roles

Which Tableau user role has the ability to publish data sources and create new projects but cannot manage site settings?

A Site Administrator

B Publisher

C Interactor

D Viewer

💡 Hint

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.

🎯 Scenario

intermediate

Assigning Permissions for Dashboard Editing

You want a user to edit existing dashboards but not delete them or change permissions. Which permission setting should you assign?

A Allow 'Edit' and 'View' permissions, deny 'Delete' and 'Change Permissions'

B Allow 'Delete' and 'Edit' permissions, deny 'View'

C Allow 'View' permission only

D Allow 'Change Permissions' and 'Delete' permissions

💡 Hint

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.

❓ dax_lod_result

advanced

Calculating Effective Permissions with Nested Roles

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?

A The user has no permission because conflicts cancel out

B The user is allowed 'View' permission because allow overrides deny

C The user is denied 'View' permission because deny overrides allow

D The user must be assigned a new role to resolve the conflict

💡 Hint

Consider Tableau's permission precedence rules.

In Tableau, deny permissions take precedence over allow permissions, so the user is denied 'View' permission.

🔧 Formula Fix

advanced

Troubleshooting Permission Issues

A user reports they cannot access a published dashboard despite being assigned the 'Interactor' role. Which of the following is the most likely cause?

A The dashboard permissions explicitly deny access to the user or their group

B The user’s browser cache is full

C The user has not logged out and back in after role assignment

D The user’s Tableau Desktop version is outdated

💡 Hint

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.

❓ visualization

expert

Designing a Permission Overview Dashboard

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?

A Use a line chart showing permission changes over time for each user

B Create a pie chart for each user showing the percentage of projects they can access

C Display a text table listing users and their roles without project details

D Use a matrix with users as rows, projects as columns, and color-coded cells for permission levels

💡 Hint

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.

Practice

1.

Which Tableau user role is primarily designed to only view and interact with dashboards without editing capabilities?

easy

A. Creator

B. Explorer

C. Viewer

D. Administrator

Solution

1. Step 1: Understand Tableau user roles

   Tableau defines roles based on user capabilities: Viewer can only view content, Explorer can interact and modify some content, Creator can build and publish content.

2. Step 2: Match role to description

   The role that only views and interacts without editing is Viewer.

3. Final Answer:

   Viewer -> Option C

4. Quick Check:

   User role for viewing only = Viewer [OK]

Hint: Viewer role means view-only access, no editing allowed [OK]

Common Mistakes:

• Confusing Explorer with Viewer
• Thinking Creator cannot edit
• Assuming Administrator is a basic role

2.

Which of the following is the correct way to assign a permission in Tableau to allow a user to publish new content?

Options:
A) Set 'Download' permission to 'Allow' for the user
B) Set 'View' permission to 'Deny' for the user
C) Set 'Publish' permission to 'Allow' for the user
D) Set 'Edit' permission to 'Deny' for the user

easy

A. Set 'Download' permission to 'Allow' for the user

B. Set 'View' permission to 'Deny' for the user

C. Set 'Edit' permission to 'Deny' for the user

D. Set 'Publish' permission to 'Allow' for the user

Solution

1. Step 1: Identify permission needed to publish content

   Publishing new content requires the 'Publish' permission to be allowed.

2. Step 2: Evaluate options

   Only Set 'Publish' permission to 'Allow' for the user correctly sets 'Publish' permission to 'Allow'. Other options either deny view or edit or allow download, which do not enable publishing.

3. Final Answer:

   Set 'Publish' permission to 'Allow' for the user -> Option D

4. Quick Check:

   Publishing requires 'Publish' permission allowed [OK]

Hint: Publishing needs 'Publish' permission set to Allow [OK]

Common Mistakes:

• Confusing 'Download' with 'Publish' permission
• Denying 'View' permission disables access
• Assuming 'Edit' permission allows publishing

3.

Given a Tableau project where a user has the following permissions:
View: Allow
Edit: Deny
Download: Allow
What will the user be able to do?

medium

A. Edit and download content but cannot view

B. View and download content but cannot edit

C. Only view content, no download or edit

D. Download content only, no view or edit

Solution

1. Step 1: Analyze each permission

   User has 'View' allowed, so can see content. 'Edit' is denied, so cannot change content. 'Download' is allowed, so can save content locally.

2. Step 2: Combine permissions to determine capabilities

   User can view and download content but cannot edit it.

3. Final Answer:

   View and download content but cannot edit -> Option B

4. Quick Check:

   View + Download allowed, Edit denied = View and download content but cannot edit [OK]

Hint: Allow view and download but deny edit means no changes allowed [OK]

Common Mistakes:

• Assuming denied edit means no view
• Confusing download with edit
• Thinking download requires edit permission

4.

Identify the error in this Tableau permission setup:
User Role: Explorer
Permissions: View - Deny, Edit - Allow
What is wrong with this configuration?

medium

A. You cannot allow Edit permission if View is denied

B. Explorer role cannot have Edit permission

C. View permission must be Deny if Edit is Deny

D. No error, this setup is valid

Solution

1. Step 1: Understand permission dependencies

   In Tableau, Edit permission requires View permission to be allowed first because you must see content to edit it.

2. Step 2: Analyze given permissions

   View is denied but Edit is allowed, which is contradictory and invalid.

3. Final Answer:

   You cannot allow Edit permission if View is denied -> Option A

4. Quick Check:

   Edit permission requires View allowed [OK]

Hint: Edit permission needs View allowed first [OK]

Common Mistakes:

• Allowing Edit but denying View
• Thinking Explorer cannot edit
• Assuming Deny on View allows Edit

5.

You manage a Tableau Server with multiple projects. You want to allow a group of users to explore and modify existing dashboards but prevent them from publishing new content. Which role and permission setup should you assign?

hard

A. Assign Explorer role with 'Publish' permission set to Deny

B. Assign Viewer role with 'Edit' permission set to Allow

C. Assign Creator role with 'Publish' permission set to Allow

D. Assign Explorer role with 'View' permission set to Deny

Solution

1. Step 1: Identify role for exploring and modifying dashboards

   The Explorer role allows users to interact with and modify existing dashboards but not create new ones.

2. Step 2: Set permissions to prevent publishing

   To prevent publishing new content, set the 'Publish' permission to Deny for this group.

3. Step 3: Evaluate options

   Assign Explorer role with 'Publish' permission set to Deny correctly assigns Explorer role and denies Publish permission. Other options either allow publishing or deny necessary permissions.

4. Final Answer:

   Assign Explorer role with 'Publish' permission set to Deny -> Option A

5. Quick Check:

   Explorer + Deny Publish = modify only, no new content [OK]

Hint: Explorer role + deny Publish stops new content creation [OK]

Common Mistakes:

• Assigning Viewer role for editing
• Allowing Publish permission by mistake
• Denying View permission disables access