Managing Projects and Workbooks in Tableau

Course: Tableau Training | Topic: Managing Projects and Workbooks | Level: Beginner to Advanced

Managing projects and workbooks is an essential Tableau administration skill. It involves organizing published content, maintaining workbook versions, controlling access, moving content between projects, updating dashboards, and ensuring that users can easily find and use the correct reports.

Explore Tableau Training

Register for a Tableau Course Demo

1. Introduction to Managing Projects and Workbooks

Tableau Server and Tableau Cloud provide environments where organizations publish, organize, share, and manage analytical content. Projects and workbooks are two important parts of this environment.

A project is a container used to organize Tableau content, such as workbooks and data sources. Projects can also support content discovery, permission management, and delegated administration.

A workbook contains analytical content such as worksheets, dashboards, stories, calculations, and data connection definitions. A published workbook allows authorized users to access visualizations through the Tableau site.

Example

A company has Sales, Finance, Marketing, and Human Resources departments. Each department creates several dashboards. An administrator creates separate projects for each department and organizes the corresponding workbooks within them. The administrator then configures permissions so that employees can access the content they need.

Main objectives

• Organize published workbooks and data sources.
• Create projects and nested project hierarchies.
• Manage workbook ownership and permissions.
• Update and replace published workbooks safely.
• Move content between projects.
• Maintain clear naming conventions and descriptions.
• Support collaboration between analysts and business users.
• Improve content security, discoverability, and maintenance.

2. Understanding Tableau Projects

A Tableau project is a logical container for organizing content on Tableau Server or Tableau Cloud. Projects help users navigate published assets and enable administrators to manage permissions at an organizational or departmental level.

Key features of projects

• Content organization: Groups related workbooks and data sources.
• Access management: Provides a place to configure default content permissions.
• Nested projects: Supports parent-child project hierarchies.
• Descriptions: Explain the purpose and intended use of a project.
• Project ownership: Identifies the user responsible for the project.
• Project leaders: Allow authorized users to manage project content without necessarily having site-wide administrative access.
• Permission inheritance: Allows content to receive permissions according to project configuration.

Example project structure

Tableau Site
├── Sales Analytics
│   ├── Regional Sales Dashboard
│   ├── Monthly Sales Report
│   └── Sales Data Source
├── Finance Analytics
│   ├── Profitability Dashboard
│   └── Budget Report
├── Marketing Analytics
│   ├── Campaign Performance
│   └── Lead Conversion Report
└── HR Analytics
    ├── Recruitment Dashboard
    └── Employee Overview

This structure makes it easier to find related content and apply suitable access rules to each department.

3. Understanding Tableau Workbooks

A workbook is a collection of analytical views created in Tableau. It can contain worksheets, dashboards, stories, calculated fields, filters, parameters, formatting, and data connection definitions.

Common workbook components

• Worksheets: Individual charts, tables, maps, and other visualizations.
• Dashboards: Collections of visualizations arranged into one analytical view.
• Stories: Sequences of views used to communicate findings.
• Filters: Controls that restrict the data displayed in views.
• Parameters: User-controlled values that can influence calculations or visualizations.
• Calculated fields: Fields created using formulas.
• Data connections: References to embedded or published data sources.

Common workbook file formats

Important: A workbook file does not necessarily contain all data or credentials required to reconnect to an external source. Check the connection configuration when transferring workbooks between environments.

4. Creating a Project in Tableau

Creating projects allows an organization to organize published content according to departments, teams, subject areas, or stages of development.

Step-by-step procedure

1. Sign in to Tableau Server or Tableau Cloud with an account that has the required project-creation permissions.
2. Open the Explore area of the site.
3. Open the New menu and select Project, where available.
4. Enter a descriptive project name.
5. Add a description explaining the purpose of the project.
6. Review the default permission settings and adjust them if authorized.
7. Save the project.
8. Open the project and verify that it appears in the expected location.

Example

Project name: Sales Analytics

Description: Contains sales dashboards, regional performance reports, and approved sales data sources for business analysis.

Best practices

• Use meaningful project names.
• Avoid creating unnecessary duplicate projects.
• Use descriptions to explain the intended audience and content.
• Establish permission standards before publishing large amounts of content.
• Assign project ownership to an appropriate responsible user.

Top-level project creation is generally an administrator capability. Creating nested projects may be available to project owners or project leaders with the required permissions.

5. Creating and Managing Nested Projects

A nested project is a project located inside another project. Nested projects help organizations create a hierarchy without making the top-level project list excessively long.

Example

Sales Analytics
├── Development
├── Testing
└── Production

In this example, the Sales Analytics project contains three child projects for different stages of the content lifecycle.

Steps to create a nested project

1. Open the parent project.
2. Open the available project-creation menu.
3. Select the option to create a project within the parent project.
4. Enter the child project's name and description.
5. Review the inherited permission rules.
6. Save and confirm the project hierarchy.

Benefits of nested projects

• Improves navigation when an organization has many workbooks.
• Separates content by team, business function, or development stage.
• Supports more structured permission management.
• Allows project leaders to manage appropriate parts of a hierarchy.

Important: Permission inheritance depends on project configuration. Moving projects or changing a parent project's permission settings can affect access to content in the hierarchy. Review the destination project's rules before making changes.

6. Organizing Workbooks Within Projects

Workbooks should be stored in projects that reflect their business purpose and intended audience. A well-organized project makes content easier to discover and maintain.

Example organization

Organizational guidelines

• Keep related workbooks in the same project when their access requirements align.
• Separate confidential content from general business reports.
• Use consistent naming conventions across departments.
• Include a meaningful description for important workbooks.
• Remove obsolete or duplicate content according to retention policies.
• Make the content owner or responsible team clear.

7. Publishing a Workbook to a Project

When a workbook is published from Tableau Desktop, the user selects the destination project. The destination determines where the workbook appears and can influence the default permissions applied to it.

Step-by-step procedure

1. Open the workbook in Tableau Desktop.
2. Sign in to the intended Tableau Server or Tableau Cloud site.
3. Select Server > Publish Workbook.
4. Choose the destination project.
5. Enter the workbook name and description.
6. Review sheets, connection settings, and authentication options.
7. Review the available permissions settings.
8. Click Publish.
9. Open the published workbook in a browser.
10. Verify that the workbook displays correctly and that intended users can access it.

Before publishing, verify

• The workbook opens without errors.
• Charts, filters, calculations, and dashboards work correctly.
• The intended data source is selected.
• The destination project is correct.
• The workbook contains no unnecessary confidential information.
• The appropriate users have access.

8. Managing Workbook Permissions

Permissions determine what users can do with a published workbook. Depending on the site's configuration, capabilities may include viewing, interacting with, downloading, editing, publishing, deleting, or changing permissions.

Common permission capabilities

The exact capabilities available depend on the content type, site role, permission rules, and Tableau deployment.

Steps to review workbook permissions

1. Open the project or locate the published workbook.
2. Open the workbook's Actions menu.
3. Select Permissions, if available.
4. Review the existing users, groups, permission templates, and capabilities.
5. Make changes only if you have the required authority.
6. Save the changes and test access using an appropriate account.

Best practices

• Grant only the capabilities users need.
• Prefer group-based permission management over maintaining many individual user rules.
• Review permissions regularly.
• Avoid giving every user publishing or editing rights.
• Test permissions after changing project or workbook settings.

9. Understanding Project-Level Permission Inheritance

Project-level permissions can establish default access rules for workbooks and other content stored in a project. Tableau supports project permission configurations that are commonly described as Locked and Customizable.

Locked permissions

When asset permissions are locked for a project, project-level rules are enforced for the relevant content. Content owners generally cannot independently change the permission rules that the locked project controls.

Customizable permissions

When asset permissions are customizable, project-level rules provide defaults, but eligible users may be able to modify permissions on individual content items.

Recommendation: Choose a permission model that matches the organization's governance requirements. Always test the effective permissions before rolling out changes to a project hierarchy.

10. Managing Workbook Ownership

Workbook ownership identifies the user responsible for the published workbook. Ownership is important because content owners may have capabilities to update, manage, or delete content, depending on site roles and permission settings.

Why ownership matters

• Helps identify the person responsible for maintenance.
• Supports troubleshooting and communication.
• Helps administrators manage content when employees change roles.
• Clarifies responsibility for updates and data quality.

Ownership management practices

1. Identify the current workbook owner.
2. Confirm that the owner is still responsible for the content.
3. Identify an appropriate replacement when ownership must change.
4. Use the available administrative or content-management workflow to change ownership.
5. Verify that the new owner has the necessary site role and access.
6. Check that connections, extracts, and scheduled refreshes continue to work.

Ownership transfer options depend on the Tableau deployment and the permissions of the users involved. A change of ownership does not automatically resolve every credential or data-connection issue.

11. Updating and Republishing Workbooks

Published workbooks often need updates when business requirements, calculations, data sources, or dashboard layouts change.

Step-by-step update process

1. Open the original workbook in Tableau Desktop or use a supported web-authoring workflow.
2. Review the requested changes.
3. Update calculations, charts, filters, dashboard layout, or data connections.
4. Validate the updated workbook against the source data.
5. Sign in to the correct Tableau site.
6. Publish the workbook to the intended project.
7. Confirm that you are updating the correct existing workbook rather than unintentionally creating a duplicate.
8. Review the connection and authentication settings.
9. Publish the update.
10. Open the published workbook and test the revised content.

Examples of workbook updates

• Adding a new chart to an existing dashboard.
• Changing the sales calculation.
• Adding a date filter.
• Updating dashboard titles and descriptions.
• Replacing a data source.
• Improving dashboard performance.

Important: Changes to a shared published data source may affect several workbooks. Check downstream dependencies before renaming or removing fields, changing data types, or modifying calculations.

12. Moving Workbooks Between Projects

Moving a workbook to another project can help reorganize content when a report changes ownership, department, or lifecycle stage.

Step-by-step procedure

1. Sign in to Tableau Server or Tableau Cloud with the required permissions.
2. Locate the workbook you want to move.
3. Open the workbook's Actions menu or select it in the content-management interface.
4. Choose the available Move option.
5. Select the destination project.
6. Review any warning about permissions or content dependencies.
7. Confirm the move.
8. Open the workbook from its new project location.
9. Test user access and verify that connections and related content continue to work.

Important considerations

• The user must have the required permissions to move the workbook.
• The destination project's permission configuration can affect the workbook's effective access rules.
• Users who could access the workbook previously may lose access if the destination project has different permissions.
• Check links, subscriptions, connected content, and documented references after reorganizing content.

13. Renaming Workbooks and Projects

Clear names help users identify the correct content. Renaming a workbook or project should be done carefully so that users understand the change and existing references can be reviewed.

Recommended naming conventions

• Use descriptive business terms.
• Keep names consistent across departments.
• Avoid names such as Final2, TestNew, or Untitled.
• Include a subject or reporting period when appropriate.
• Use descriptions to document the workbook's purpose and intended audience.

Examples

Renaming procedure

1. Locate the project or workbook.
2. Open the available editing or actions menu.
3. Select the rename or edit-details option.
4. Enter the new name.
5. Save the change.
6. Verify the updated name and review any links or references that users rely on.

14. Deleting and Archiving Workbooks

Deleting obsolete workbooks can reduce clutter, but it should be performed only after checking ownership, usage, dependencies, and retention requirements.

Before deleting a workbook

• Confirm that the workbook is no longer required.
• Check whether users depend on its dashboards or links.
• Review subscriptions and related documentation.
• Check whether it is referenced in collections or other workflows.
• Confirm that a backup or approved archive exists if required.
• Obtain the necessary approval from the content owner or administrator.

Deletion workflow

1. Locate the workbook in the appropriate project.
2. Verify that it is the correct content item.
3. Open the actions menu.
4. Select the delete option, if authorized.
5. Confirm the deletion.
6. Notify affected users when appropriate.

Important: Deletion can be difficult or impossible to reverse through the normal interface. Deleting a project can also delete its contained workbooks and nested projects. Move content to another project before deleting a project if the content must be retained.

15. Managing Workbooks in Development, Testing, and Production

Organizations often separate workbooks into development, testing, and production stages to reduce the risk of introducing errors into business-critical reports.

Example lifecycle

Development
    |
    v
Testing / Validation
    |
    v
Production
    |
    v
Monitoring and Maintenance

Development

Analysts create and modify visualizations, test calculations, and experiment with data models.

Testing

Analysts and business stakeholders validate data accuracy, dashboard behavior, access permissions, and performance.

Production

The approved workbook is published to the project intended for regular business use. Permissions and refresh processes should follow the organization's governance standards.

Monitoring and maintenance

Owners review refresh failures, data quality, content usage, and requests for improvements.

Separating lifecycle stages helps reduce accidental changes to production reports. Tableau projects and permissions can support this workflow, but the exact publishing and promotion process depends on the organization's deployment and governance procedures.

16. Managing Workbook Performance

A workbook that loads slowly can reduce user productivity. Workbook management includes reviewing performance as data volumes and business requirements change.

Common causes of slow performance

• Large data volumes.
• Complex calculations.
• Too many worksheets or dashboard objects.
• Excessive marks or detailed visualizations.
• Inefficient joins or data models.
• Slow underlying database queries.
• Too many filters or expensive filter interactions.
• Network or infrastructure limitations.

Performance improvement practices

• Remove unused fields and unnecessary worksheets.
• Reduce unnecessary marks and visual complexity.
• Optimize calculations and data-model design.
• Choose live connections or extracts based on actual requirements.
• Reduce unnecessary data where appropriate.
• Use Tableau's performance analysis tools where available.
• Test the published workbook under realistic conditions.

17. Managing Workbooks and Data Sources Together

A workbook may use an embedded data source or a separately published data source. Understanding this relationship is important when managing and updating content.

Best practices

• Use published data sources when shared definitions and centralized management are valuable.
• Document important data-source dependencies.
• Test changes before updating a source used by multiple workbooks.
• Review credentials and refresh settings after ownership or connection changes.
• Keep workbook and data-source names consistent with business terminology.

18. Project and Workbook Management Troubleshooting

19. Best Practices for Managing Projects and Workbooks

• Create a clear project hierarchy before publishing large amounts of content.
• Organize content by business purpose and audience.
• Use consistent naming conventions and descriptions.
• Manage permissions at the project level where appropriate.
• Prefer groups over individual user rules for scalable access management.
• Use locked project permissions when consistent governance is required.
• Assign appropriate owners and project leaders.
• Validate workbook data and calculations before publishing updates.
• Review the destination project's permissions before moving content.
• Keep development, testing, and production content separate where appropriate.
• Check dependencies before changing shared data sources.
• Monitor workbook performance and extract-refresh status.
• Remove obsolete content according to an approved retention policy.
• Test published content using the permissions of the intended audience.
• Document critical dashboards, data owners, and refresh requirements.

20. Practical Project: Organizing a Company's Tableau Content

Scenario

A company has multiple teams publishing Tableau dashboards. Employees struggle to find the right reports, and some users can access content they do not need. The company wants a more organized and secure Tableau site.

Step 1: Plan the project structure

Create a proposed hierarchy:

Company Analytics
├── Sales Analytics
├── Finance Analytics
├── Marketing Analytics
└── HR Analytics

Step 2: Identify content owners

Assign appropriate owners or project leaders to manage content for each department.

Step 3: Organize existing workbooks

Move each workbook to the appropriate project after checking dependencies and destination permissions.

Step 4: Configure access rules

Give each group the capabilities it needs. For example, analysts may need publishing capabilities, while business managers may need only to view and interact with dashboards.

Step 5: Standardize workbook metadata

Use clear names, descriptions, and tags so users can find relevant reports quickly.

Step 6: Validate content

Open each important workbook, check its data, and verify that the intended audience can access it.

Step 7: Establish maintenance procedures

Define who updates the workbooks, monitors data freshness, handles access requests, and reviews obsolete content.

Expected outcome

The Tableau site becomes easier to navigate, permissions are more consistent, and departments have clear responsibility for maintaining their reports.

21. Interview Questions and Answers

Q1. What is a project in Tableau?

Answer: A project is a container used to organize Tableau content such as workbooks and data sources. It also supports content discovery and permission management.

Q2. What is a workbook in Tableau?

Answer: A workbook contains worksheets, dashboards, stories, calculations, and data connection definitions used for analysis.

Q3. Why are projects important?

Answer: Projects organize content, improve navigation, support permission management, and help teams manage their published assets.

Q4. What is a nested project?

Answer: A nested project is a child project located inside another project. It supports hierarchical content organization.

Q5. How do you publish a workbook to a project?

Answer: Open the workbook, sign in to the Tableau site, select Server > Publish Workbook, choose the destination project, configure the required settings, publish, and verify the result.

Q6. What are project-level permissions?

Answer: Project-level permissions define access rules for a project and can establish default permissions for workbooks and other content within it.

Q7. What is the difference between locked and customizable project permissions?

Answer: Locked permissions enforce the relevant project rules for managed content. Customizable permissions allow eligible users to modify individual content permissions.

Q8. What is workbook ownership?

Answer: Workbook ownership identifies the user responsible for a published workbook and can affect content-management capabilities.

Q9. How can you update a published workbook?

Answer: Edit the workbook, validate the changes, publish to the correct destination, and confirm that the existing published content has been updated as intended.

Q10. Why might users lose access after a workbook is moved?

Answer: The destination project may apply different permission rules, changing the workbook's effective access.

Q11. What should you check before deleting a project?

Answer: Check all contained workbooks, nested projects, ownership, dependencies, and retention requirements. Move any required content before deletion.

Q12. Why should permissions be managed through groups?

Answer: Group-based permissions are easier to maintain and scale than creating separate rules for many individual users.

Q13. How do you improve workbook performance?

Answer: Optimize data models and calculations, reduce unnecessary visual elements, choose suitable connection types, and test performance.

Q14. What is the purpose of a project leader?

Answer: A project leader can manage a project and its content within the capabilities permitted by their site role, without necessarily having site-wide administrative privileges.

Q15. Why is testing important after moving or updating a workbook?

Answer: Testing confirms that the workbook displays correctly, its data connections work, and the intended users have the correct access.

22. Practical Exercises

1. Create a proposed Tableau project hierarchy for Sales, Finance, and Marketing.
2. Write descriptions for three projects.
3. Create a workbook naming convention for monthly reports.
4. Publish a sample workbook to an appropriate project.
5. Review the workbook's permissions.
6. Explain the difference between locked and customizable permissions.
7. Move a test workbook to another project, if your environment permits it.
8. Update a workbook and verify the published version.
9. Identify possible dependencies before deleting a test workbook.
10. Document a process for reviewing workbook ownership and data freshness.

Practice checklist

• Understand projects and workbooks.
• Know how to create projects and nested projects.
• Understand project-level permission inheritance.
• Know how to publish and update workbooks.
• Understand ownership and project-leader responsibilities.
• Know how to move and rename content.
• Understand the risks of deleting projects and workbooks.
• Apply naming, security, and performance best practices.

23. Quick Revision Notes

• Project: Organizes published Tableau content.
• Workbook: Contains worksheets, dashboards, stories, and connection definitions.
• Nested project: A child project within a parent project.
• Publishing: Makes a workbook available on Tableau Server or Tableau Cloud according to its permissions.
• Ownership: Identifies the responsible content owner.
• Project leader: Manages a project within the capabilities permitted by their site role.
• Locked permissions: Enforce relevant project-level permission rules for managed content.
• Customizable permissions: Allow eligible users to modify individual content permissions.
• Move content: Can change effective access because destination permissions may differ.
• Republish: Updates published content when the correct existing destination is selected.
• Deletion: Can permanently remove content and should follow an approved process.
• Best practice: Use clear project structures, group-based permissions, meaningful metadata, and regular validation.

24. Official Tableau Learning Resources

• Use Projects to Manage Content Access
• Manage Permissions with Projects
• Add Projects and Move Content Into Them
• Configure Projects, Groups, and Permissions
• Let Users Request Access to Content and Projects

25. Conclusion

Managing projects and workbooks is essential for maintaining an organized, secure, and efficient Tableau environment. Projects provide a structure for organizing content and managing access, while workbooks deliver the dashboards and analytical views that users need.

Effective management includes establishing clear project hierarchies, applying appropriate permissions, maintaining workbook ownership, updating content carefully, reviewing dependencies, and validating access after changes. These practices help organizations maintain trustworthy dashboards and make their analytical content easier to discover and use.

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