User permissions and roles in Tableau - Step-by-Step Guide

Introduction

User permissions and roles in Tableau control who can see and change content. This helps keep your data safe and organized by giving the right access to the right people.

When you want only managers to edit dashboards but let everyone view them

When you need to restrict sensitive sales data to the sales team only

When you want to allow some users to publish new reports but others only to view

When you want to create groups for departments and assign permissions to the group

When you want to prevent accidental changes by limiting editing rights

Steps

Step 1: Sign in

- Tableau Server or Tableau Online homepage

You see the main content page with projects and workbooks

Step 2: Click

- Content item (project, workbook, or view) you want to set permissions for

The content details page opens

Step 3: Click

- Permissions tab or Permissions option in the menu

The permissions page shows current users and groups with their roles

Step 4: Click

- Add a user or group button

A list of users and groups appears for selection

Step 5: Select

- User or group from the list

The selected user or group is added to the permissions list

Step 6: Choose

- Role dropdown next to the user or group

The role is assigned and permissions update accordingly

💡 Roles like Viewer, Explorer, Explorer (Can Publish), and Creator control what users can do

Step 7: Click

- Save or Apply button

Permissions changes are saved and take effect immediately

Before vs After

Before

All users see and can edit all dashboards and data sources

After

Only users with Explorer or Creator roles can edit; Viewers can only see dashboards

Settings Reference

Role assignment

📍 Permissions page next to each user or group

Defines what actions a user or group can perform on content

Default: Viewer

Add user or group

📍 Permissions page, Add button

Selects who will get specific permissions

Default: None selected

Project permissions inheritance

📍 Project settings

Controls if permissions flow down from parent project or are unique

Default: Inherit permissions from parent project

Common Mistakes

Assigning permissions directly to many individual users

It becomes hard to manage and track who has access

Use groups to assign permissions to multiple users at once

Not saving permissions after changes

Changes will not apply and users keep old access

Always click Save or Apply after editing permissions

Giving Creator role to all users

Users may accidentally change or delete important content

Assign Creator role only to trusted users who build content

Summary

User permissions and roles control who can view or edit Tableau content

Assign roles to users or groups on the Permissions page for projects or workbooks

Use groups and save changes to keep permissions organized and effective

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