Sharing Dashboards and Managing Published Content in Tableau

Topic: Sharing Interactive Dashboards, Publishing Workbooks, Managing Published Content, Controlling Access, and Maintaining Tableau Resources.

Course Link: Explore Tableau Training

Demo Link: Register for a Tableau Course Demo

1. Introduction to Sharing Dashboards and Managing Published Content

Tableau is a business intelligence and data visualization platform that enables users to analyze data, create interactive dashboards, build reports, and share business insights. After creating a dashboard in Tableau Desktop or Tableau web authoring, users can publish it to Tableau Server or Tableau Cloud so that authorized people can access it through a web browser.

Sharing dashboards means making visualizations available to other users so they can view, interact with, and analyze information according to their permissions.

Managing published content means organizing, updating, securing, maintaining, and controlling access to workbooks, dashboards, views, projects, and published data sources.

Why Are These Skills Important?

• Help teams collaborate using a common set of dashboards.
• Allow business users to access reports without installing Tableau Desktop.
• Make important business information easier to distribute.
• Support centralized management of workbooks and data sources.
• Help administrators control access to confidential information.
• Reduce duplicate reports and inconsistent versions of data.
• Make it easier to maintain, update, and monitor published content.

Tableau supports sharing content directly with other users, copying links, and embedding views in supported webpages. Recipients still need the appropriate access to view the content. Read the official Tableau guide to sharing web content.

2. Understanding Published Content in Tableau

Published content is Tableau content stored on Tableau Server or Tableau Cloud so that authorized users can access it. Publishing makes it possible to distribute analysis across a team or organization.

2.1 Workbook

A workbook is a Tableau file or published resource that can contain worksheets, dashboards, stories, and data connection information. It may contain one or more visualizations designed to answer business questions.

Example: A Sales Performance workbook contains worksheets for revenue, profit, product categories, and regional sales, together with an interactive dashboard.

2.2 Dashboard

A dashboard combines multiple worksheets and other supported elements into a single interactive analytical view. Users can explore data through filters, highlighting, selections, and other configured interactions.

Example: A management dashboard displays total revenue, monthly sales trends, regional performance, and top-selling products on one screen.

2.3 View

A view is a particular visualization created in Tableau. It can be a chart, table, map, or another supported visual representation. A dashboard can contain several views.

2.4 Published Data Source

A published data source is a centrally available data connection that authorized users can reuse when creating workbooks. Depending on the configuration, it may use a live connection or an extract.

2.5 Project

A project is a container used to organize Tableau content. Projects can group workbooks, data sources, and other resources according to departments, business functions, or access requirements.

2.6 Story

A Tableau story presents a sequence of visualizations or story points to communicate findings in a particular order. Stories can be published and shared along with other supported Tableau content.

Published Content Comparison

3. Tableau Desktop, Tableau Server, and Tableau Cloud

Understanding the purpose of each Tableau environment helps you select the correct way to publish and share content.

3.1 Tableau Desktop

Tableau Desktop is an authoring application used to connect to data, create worksheets, design dashboards, and prepare workbooks for publishing.

Example: A developer creates a dashboard using a sales Excel file and prepares it for publication.

3.2 Tableau Server

Tableau Server is a platform organizations can deploy and manage to publish, share, and govern Tableau content. It can be hosted in an organization's own environment or in a supported infrastructure arrangement.

Example: A company hosts Tableau Server for employees who need secure access to internal reports.

3.3 Tableau Cloud

Tableau Cloud is Tableau's hosted analytics platform. It allows organizations to publish and manage content without operating their own Tableau Server infrastructure.

Example: A distributed team uses Tableau Cloud to access approved dashboards from different locations.

4. How to Publish a Workbook to Tableau Server or Tableau Cloud

Publishing transfers a workbook from Tableau Desktop to a shared Tableau environment. Once published, authorized users can access the workbook through the web interface or supported Tableau applications.

Step-by-Step Procedure

1. Open the completed workbook in Tableau Desktop.
2. Review the worksheets, dashboards, filters, calculations, and data connections.
3. Sign in to the appropriate Tableau Server or Tableau Cloud site.
4. Select Server > Publish Workbook.
5. Enter a clear workbook name.
6. Select the destination project.
7. Review the data connection, authentication, and extract settings.
8. Configure permissions or publishing options when available and appropriate.
9. Select Publish.
10. Wait for the publishing process to complete.
11. Open the published workbook in a browser.
12. Test the dashboard, filters, and data access using an account with the intended permissions.

Example

A sales analyst creates a workbook called Monthly Sales Performance. The analyst publishes it to the Sales Analytics project on Tableau Cloud. Sales managers with the appropriate permissions can now open the workbook and explore the published dashboard.

Important: Publishing does not automatically make content accessible to every user. The user's site membership, site role, and content permissions determine whether they can access it and what they can do.

Read Tableau's official publishing overview.

5. Different Ways to Share Tableau Dashboards

Tableau offers several ways to distribute published dashboards. The appropriate method depends on the intended audience, the security requirements, and how recipients will use the information.

5.1 Share Directly with Users

You can share supported content with specific users through Tableau's sharing interface. Depending on the site configuration, the recipient may receive a notification and find the item under Shared with Me.

Steps:

1. Sign in to Tableau Server or Tableau Cloud.
2. Open the workbook or view you want to share.
3. Open the Actions menu, usually represented by three dots.
4. Select Share.
5. Enter the intended user's name or select the available recipient.
6. Add an optional message.
7. Share the content.
8. Verify that the recipient has permission to view it.

5.2 Share a Link

A link allows you to distribute a URL to a published workbook or view through an approved communication channel, such as email, a team chat, or an internal knowledge page.

Steps:

1. Open the published view.
2. Select Share from the toolbar or Actions menu.
3. Choose Copy Link when available.
4. Paste the link into the intended communication channel.
5. Confirm that recipients have access to the Tableau site and the content.

A link does not automatically grant access. If the recipient lacks the necessary permissions, they may be unable to open the content or may need to request access.

5.3 Share Through a Project

When several users need the same dashboards, placing content in a project with suitable group permissions can be more manageable than sharing every workbook individually.

Example: A Finance Analytics project contains approved finance dashboards. Members of the Finance Viewers group receive the access they need through the project's permission rules.

5.4 Embed a View in a Webpage

Tableau provides supported embedding options for views. Embedding allows an interactive visualization to appear within another webpage or application.

Typical workflow:

1. Open the published view.
2. Choose the Share option.
3. Select Copy Embed Code if available.
4. Insert the generated code into the appropriate webpage or application according to the site's integration requirements.
5. Test the embedded view and confirm that authentication and access permissions work as expected.

Security note: Embedding a view does not automatically make private content public. Authentication, site configuration, and permissions continue to affect access. Only publish content publicly when you intentionally want the data to be accessible to the public.

5.5 Share Through Tableau Mobile

Authorized users can access supported Tableau content through the Tableau Mobile app. The user still needs the appropriate account, connectivity, and permissions to view the published content.

Sharing Methods Comparison

Official documentation: Sharing and embedding Tableau content.

6. Understanding Permissions When Sharing Dashboards

Permissions determine what users can do with published content. For example, a user may be allowed to view a dashboard but not edit, download, publish, or delete the underlying workbook.

Common Capabilities

• View: Open and interact with authorized content.
• Web Edit: Edit supported content in the browser when the role and configuration permit it.
• Download: Download supported content or data when permitted.
• Publish: Publish eligible content to an authorized project.
• Save or Overwrite: Save changes or replace existing content when permitted.
• Delete: Remove content when authorized.
• Set Permissions: Manage access rules where the user has the required authority.

The capabilities available for a particular content type depend on the Tableau version, site role, license, and permission configuration.

Example: View-Only Access

A company wants all sales employees to view the monthly sales dashboard but does not want them to modify the published workbook.

Administrators should review all applicable rules, including project-level rules, group permissions, and broad groups such as All Users. The effective permission outcome depends on how Tableau evaluates those rules and the user's maximum capabilities.

Read the official Tableau permissions guide.

7. Managing Published Content Using Projects

Projects provide a structured way to organize published Tableau content. A well-planned project structure makes content easier to locate, secure, maintain, and administer.

Examples of Project Organization

• Sales Analytics: Sales performance, revenue trends, and regional reports.
• Finance Analytics: Budgets, expenses, profitability, and financial summaries.
• HR Analytics: Recruitment, workforce, and employee reports with appropriate restrictions.
• Marketing Analytics: Campaign performance, leads, and customer engagement.
• Executive Dashboards: High-level performance indicators for authorized leadership.

How to Organize Content

1. Identify the main business departments or reporting functions.
2. Create projects with clear and consistent names.
3. Publish related workbooks and data sources to the correct projects.
4. Assign appropriate permissions to groups.
5. Decide whether project permissions should be locked or customizable, according to governance requirements.
6. Document ownership and the purpose of each project.
7. Review the structure periodically and remove unnecessary duplication.

Locked and Customizable Permissions

Locked project permissions help enforce consistent permission rules for content within a project. Customizable project permissions allow eligible users to set different permissions for individual assets where supported.

Use centralized, locked permissions when consistency is important. Use customizable permissions when individual workbooks or data sources require legitimate exceptions.

8. Managing Published Workbooks

Managing published workbooks includes keeping reports organized, updating them when requirements change, reviewing access, and removing obsolete content when appropriate.

Common Workbook Management Tasks

• Rename workbooks using clear, meaningful names.
• Move workbooks to appropriate projects when permitted.
• Update workbook descriptions to explain the report's purpose.
• Review ownership and assign responsibility for important content.
• Modify permissions when audiences or responsibilities change.
• Republish workbooks when dashboards need changes.
• Review extract refresh settings where the workbook uses extracts.
• Remove obsolete or duplicate workbooks after checking dependencies.

Example: Updating a Published Sales Dashboard

A sales manager requests an additional profit-margin chart on an existing dashboard. The developer opens the workbook, adds the new chart, tests the calculations, and republishes the workbook to the approved project. The developer then verifies that the published version displays correctly and that existing users retain the intended access.

Recommended Workflow

Review Business Requirement
          |
          v
Open Workbook in Desktop or Web Authoring
          |
          v
Make and Test Changes
          |
          v
Review Data and Permissions
          |
          v
Publish or Save Changes
          |
          v
Validate Published Version
          |
          v
Notify Relevant Users

Important: Before replacing a published workbook, check whether other users rely on its views, custom views, subscriptions, embedded usage, or data connections. Test significant changes before updating business-critical content.

9. Managing Published Data Sources

Published data sources help organizations centralize data connections so multiple workbooks can use a common source. This can reduce duplicated connection configuration and make data governance easier.

Benefits

• Promotes reuse of approved data connections.
• Helps teams work from a consistent data definition.
• Can simplify connection maintenance.
• Can reduce repeated data-source setup across workbooks.
• Supports centrally managed access and refresh settings where applicable.

Common Management Tasks

1. Publish a data source to the appropriate project.
2. Set permissions for the groups that need to connect to it.
3. Configure connection authentication appropriately.
4. Schedule extract refreshes if the source uses a refreshable extract.
5. Update connection details when the underlying source changes.
6. Review dependent workbooks before changing or replacing the data source.
7. Verify that the source and connected workbooks continue to work correctly.

Example: Instead of each department creating its own separate connection to the same approved sales database, a data steward publishes a central Sales Data Source. Authorized analysts can use it to build their own reports, subject to the configured permissions.

Official documentation: Publishing workbooks and data sources.

10. Editing Published Content in Tableau Server or Tableau Cloud

Tableau supports web authoring for eligible users and content. Depending on the user's site role and permissions, a published workbook can be edited through a browser without downloading it to Tableau Desktop.

General Editing Steps

1. Sign in to Tableau Server or Tableau Cloud.
2. Open the published workbook or view.
3. Select Edit if it is available.
4. Make the required changes in web authoring.
5. Review the worksheet and dashboard layout.
6. Validate filters, calculations, and data behavior.
7. Choose the available Save, Publish, or Publish As option.
8. Verify the updated content after saving.

The available actions depend on the user's site role, permissions, content type, and product configuration. A user who can view a dashboard may not have permission to edit or save changes to the published workbook.

Official documentation: Edit Tableau views on the web.

11. Using Custom Views for Personalized Analysis

A custom view saves a particular state of interaction with a published visualization. For example, a user may apply filters, change sorting, or select specific marks and save that arrangement for future use.

A custom view does not ordinarily change the underlying published workbook. It provides a convenient way to return to a preferred view of the data.

Example

A regional sales manager regularly reviews only the West region. The manager filters the dashboard to West, changes the sorting to show the highest-performing products first, and saves the result as a custom view called West Region Performance.

General Steps

1. Open the published visualization.
2. Apply the required filters or sorting.
3. Select or highlight relevant marks if needed.
4. Select Save Custom View when available.
5. Enter a meaningful name.
6. Choose whether it should be the default view, if supported.
7. Choose whether to make it visible to others when that option is available and appropriate.
8. Save the custom view.

Important Considerations

• Custom views are associated with the original published content.
• Deleting the original content can also remove its custom views.
• Changes to the original workbook may affect custom views.
• Visibility and sharing options depend on the user's role and site settings.
• Review custom-view ownership before removing a user from the site.

Official documentation: Use custom views.

12. Managing Content Ownership

Content ownership identifies the user responsible for a published workbook or data source. Ownership matters because content owners may be responsible for maintenance, publishing, and certain content-management actions.

Why Ownership Matters

• Helps identify who maintains a dashboard.
• Supports troubleshooting and change requests.
• Helps manage content when employees change teams or leave.
• Can affect who is able to update or manage published resources.
• Supports accountability for important reports.

Ownership Best Practices

1. Assign a clear owner to each business-critical workbook or data source.
2. Document the owner's team and business purpose.
3. Review ownership during employee transfers and offboarding.
4. Transfer ownership using the supported administrative process when needed.
5. Confirm that the new owner has the necessary permissions and source access.
6. Test refreshes and publishing workflows after a transfer.

Ownership transfer does not automatically resolve every permission or data-connection issue. Review credentials, refresh tasks, group access, and dependencies as part of the handover.

13. Replacing, Moving, and Deleting Published Content

Content management often includes reorganizing projects, replacing old workbook versions, and removing resources that are no longer required. These operations should be performed carefully because other users may depend on the content.

13.1 Replacing a Workbook

• Confirm that the new version has been tested.
• Check whether the workbook name and destination should remain the same.
• Review data connections and extract settings.
• Check existing permissions and ownership.
• Validate dependent views, custom views, subscriptions, and embedding after replacement.

13.2 Moving a Workbook

• Choose the correct destination project.
• Confirm that the person performing the move has the required privileges.
• Review the destination project's permission rules.
• Verify that the intended users can still access the workbook.
• Check any links, workflows, or integrations that depend on the published content.

13.3 Deleting a Workbook

• Confirm that the workbook is no longer needed.
• Check with its owner or stakeholders before deletion.
• Identify any dependent views, custom views, subscriptions, or embedded usage.
• Check whether a replacement report exists.
• Delete the content only when authorized and appropriate.

Best practice: Do not delete published content simply because it appears old. Check ownership, usage, dependencies, and business requirements first.

14. Keeping Published Dashboards Up to Date

Published dashboards must be maintained to remain useful and trustworthy. Updating the workbook design is different from updating the underlying data, so both aspects should be reviewed.

Workbook Updates

Workbook updates include changing visualizations, filters, calculations, labels, dashboard layouts, and other design elements.

Data Updates

Data updates depend on the connection type. Live connections query the underlying source when Tableau accesses the data, while extracts require an appropriate refresh process to include new source data.

Maintenance Checklist

• Confirm that the dashboard still answers the intended business questions.
• Verify calculations, filters, and data definitions.
• Check whether the source schema has changed.
• Review extract refresh schedules and recent job status.
• Confirm that the workbook uses the intended data source.
• Review permissions after changes to the audience.
• Test the published version after republishing.

15. Subscriptions and Automated Dashboard Delivery

Tableau subscriptions can send users snapshots or links to supported views on a recurring schedule, subject to site configuration and content eligibility. They are useful when people need regular reminders or updates without manually opening the dashboard every time.

Example

A sales manager subscribes to the Monthly Sales Dashboard so that the manager receives a scheduled email containing a snapshot or link to the view when the subscription runs successfully.

General Subscription Workflow

1. Open the published view.
2. Locate the Subscribe option when available.
3. Choose the supported delivery or schedule settings.
4. Confirm the recipient and view details.
5. Save the subscription.
6. Verify delivery and troubleshoot failures if needed.

Subscriptions depend on the site's configuration, permissions, and supported features. An email snapshot is not necessarily a replacement for opening the live published view, and the displayed data depends on the view and its refresh state.

16. Security Best Practices for Sharing Dashboards

Dashboards may contain confidential business information, employee information, financial data, customer details, or other sensitive material. Sharing should therefore be planned around the intended audience.

Recommended Security Practices

1. Use least privilege: Grant users only the capabilities they need.
2. Share with the correct audience: Confirm recipients before sharing restricted content.
3. Use group-based access: Apply consistent permissions to relevant departments.
4. Review broad permissions: Check All Users and other groups that may grant unexpected access.
5. Protect sensitive data: Use appropriate data-source security and row-level restrictions when required.
6. Review download permissions: Decide whether recipients need to download data or workbooks.
7. Test with ordinary accounts: Verify access using a non-administrator account with the expected role.
8. Review embedded views: Check authentication and permissions for content embedded in external applications.
9. Audit access regularly: Remove outdated permissions and users who no longer need access.
10. Avoid accidental public exposure: Never publish confidential data to Tableau Public or another public destination.

Remember: Copying a link does not make a private dashboard public, and embedding does not remove the need to configure security correctly. Always verify the actual access behavior in the intended environment.

17. Common Problems and Troubleshooting

18. Practical Project: Publish and Share a Sales Dashboard

Objective: Publish a sales dashboard, share it with the appropriate audience, and maintain its access and content settings.

Scenario

A company wants to publish a dashboard showing sales revenue, profit, monthly trends, and regional performance. Sales employees should view the dashboard, managers should analyze it, and authorized developers should maintain it.

Step 1: Prepare the Workbook

1. Connect Tableau Desktop to the sales dataset.
2. Create worksheets for revenue, profit, monthly trends, and regional performance.
3. Combine the worksheets into an interactive dashboard.
4. Add suitable filters and clear titles.
5. Validate calculations and totals.

Step 2: Publish the Workbook

1. Sign in to Tableau Server or Tableau Cloud.
2. Choose Publish Workbook.
3. Enter the name Sales Performance Dashboard.
4. Select the Sales Analytics project.
5. Review data connection and authentication settings.
6. Publish the workbook.

Step 3: Configure Access

1. Create or identify the Sales Viewers, Sales Managers, and Sales Developers groups.
2. Assign compatible site roles and licenses.
3. Grant each group the appropriate permissions.
4. Review other applicable permission rules.
5. Test access using representative accounts.

Step 4: Share the Dashboard

1. Open the published dashboard.
2. Select Share.
3. Share directly with intended users or copy a link.
4. Send the link through an approved communication channel.
5. Ask recipients to confirm that they can open the dashboard.

Step 5: Maintain Published Content

1. Document the workbook owner and business purpose.
2. Check data freshness and extract refresh settings if applicable.
3. Review permissions regularly.
4. Update the workbook when business requirements change.
5. Test the published version after each important update.
6. Remove obsolete content only after checking ownership and dependencies.

Expected Access Matrix

The matrix describes the intended outcome. Actual access depends on the assigned site roles, licenses, permissions, and project configuration.

19. Interview Questions and Answers

Q1. What does publishing a Tableau workbook mean?

Answer: Publishing places a workbook on Tableau Server or Tableau Cloud so authorized users can access and interact with the published content.

Q2. What is the difference between a workbook and a dashboard?

Answer: A workbook can contain worksheets, dashboards, stories, and data connections. A dashboard combines multiple views and other elements into a single analytical display.

Q3. How can you share a Tableau dashboard with another user?

Answer: You can use the supported Share option to share directly with a user or copy a link. The recipient must have the appropriate access to the published content.

Q4. Does sharing a link automatically grant permission?

Answer: No. A link identifies the content, but access is controlled by the user's site membership, permissions, and other security settings.

Q5. What is a published data source?

Answer: It is a centrally published data connection that authorized users can reuse to build workbooks, subject to its permissions and connection configuration.

Q6. What is a project in Tableau?

Answer: A project is a container used to organize published content and help manage permissions and access.

Q7. What is the purpose of web authoring?

Answer: Web authoring lets eligible users create or edit supported Tableau content in a browser without relying entirely on Tableau Desktop.

Q8. What is a custom view?

Answer: A custom view saves a particular state of interaction with a published visualization, such as filter selections and sorting, without ordinarily changing the underlying workbook.

Q9. What should be checked before deleting a published workbook?

Answer: Check ownership, usage, dependencies, subscriptions, custom views, embedding, and whether users still need the report.

Q10. Why is content ownership important?

Answer: Ownership helps identify who is responsible for maintaining the content, updating it, and coordinating changes or troubleshooting.

Q11. How can a company share dashboards securely?

Answer: Use least-privilege permissions, group-based access, appropriate project organization, regular access reviews, and data-level security when required.

Q12. What is the difference between a live connection and an extract?

Answer: A live connection queries the underlying source when data is requested, while an extract uses stored data that must be refreshed to reflect source changes.

Q13. Why might a user see a different dashboard result from another user?

Answer: Different filters, custom views, user-specific data restrictions, permissions, or source-data states can cause different results.

Q14. What happens when a workbook is moved to another project?

Answer: Its access may change because the destination project can have different permission rules. Effective access should be tested after the move.

Q15. What are the benefits of centralized content management?

Answer: Centralized management supports consistent organization, permission control, reusable data sources, easier maintenance, and reduced duplication.

20. Practice Exercises

1. Create a sales dashboard in Tableau Desktop and publish it to Tableau Server or Tableau Cloud.
2. Share the dashboard directly with an authorized test user.
3. Copy the dashboard link and test access using a second account.
4. Create a project structure for Sales, Finance, HR, and Marketing content.
5. Configure group permissions for viewers and developers.
6. Save a custom view with a specific region filter.
7. Update a published workbook and verify the result.
8. Review the owner and permissions of a published data source.
9. Develop a checklist for safe workbook deletion and replacement.
10. Explain how to troubleshoot a user who can open a workbook but cannot edit it.

21. Quick Revision Checklist

• Understand the purpose of publishing Tableau content.
• Know the differences between workbooks, dashboards, views, data sources, and projects.
• Understand Tableau Desktop, Server, and Cloud.
• Know how to publish a workbook.
• Understand direct sharing, copying links, and embedding.
• Remember that sharing a link does not automatically grant access.
• Understand project-level and content-level permissions.
• Know how to organize published content into projects.
• Understand custom views and their relationship to original content.
• Review ownership before transferring or removing users.
• Check dependencies before replacing, moving, or deleting workbooks.
• Verify data freshness after publishing or updating content.
• Apply least-privilege access and test with representative user accounts.

22. Conclusion

Sharing dashboards and managing published content are essential skills for Tableau developers, analysts, and administrators. Publishing makes analytical insights available to a wider audience, while sharing features help users distribute content through direct sharing, links, projects, and supported embedding options.

Effective content management also requires clear project organization, secure permissions, responsible ownership, careful workbook updates, and regular maintenance. By combining these practices, organizations can provide users with reliable dashboards while protecting important business data.

Continue Learning: Explore Tableau Training | Register for a Tableau Course Demo