Video | Tableau | Tool strategy | Data engineering

Move assets into projects: New in Tableau 2022.3

Moving external assets into projects sounds simple until you try to move them back out and your brain gets fried.

Part ofWhat's new in Tableau 2022.3
Watch on YouTube
  • In 2022.3 you can select a database under External Assets, choose Actions, and move it into a project so it's governed by that project's permissions.
  • The 'move the tables' option carries any tables sitting inside the database across with it when you move the asset.
  • Once moved, the permissions window switches to a project-style layout, whereas assets still locked to a database show a 'table permissions are locked for this database' message.
  • With Data Management enabled you can trace assets through virtual connections and tables via data lineage.
  • Removing an asset from the Tableau catalogue deletes the asset reference entirely and breaks anything connected to it, so it's not a safe way to move an asset back out of a project.

Tableau 2022.3 lets you move external assets like databases and tables into a project folder so they inherit that project's permissions, but Tim finds the feature raises more questions than it answers once you try to reverse the move.

Working from the External Assets view in Tableau, filtered down to a handful of database assets connected via Snowflake, some with Data Management enabled for lineage tracing.

The Breakdown
  1. Filter the external assets view 0:00

    From the left-hand menu, open External Assets and use the non-embedded filter and content-type drop-down to narrow the list down to just databases or just tables, which makes managing a long list far more manageable.

  2. Move a database into a project 0:49

    Select a database, choose Actions, then move it to a project folder. Anyone with access to that project can now see the asset, governed by whatever permissions you set there. Ticking 'move the tables' at this point carries across any tables sitting inside that database too.

  3. Confirm the move via the project and lineage 1:21

    Once moved, go to the project and filter by content type to check the database and its tables landed correctly. If Data Management is enabled, you can use data lineage on an asset to trace it through any virtual connections down to its underlying tables.

  4. Manage permissions at the project level 2:40

    Project permissions menus now include a 'more' option covering metrics, virtual connections, databases and tables, so you can set view permissions and capabilities for these assets right alongside everything else in the project.

  5. Spot the permissions style change once moved 5:04

    An asset still tied to its database shows a 'table permissions are locked for this database' message and inherits the database's own permissions unless you customise them independently. Once moved into a project, that same asset's permissions window switches to a project-style layout, meaning it's now delegated to and controlled by the project instead.

  6. Try to move an asset back out 7:02

    Tim attempts to move an asset from a project back to External Assets and finds no direct option to do so. Documentation only covers moving assets in, not reversing it, leaving the default 'catch-all' folder as the only apparent destination — which he flags as an unsatisfying answer since it would attach the database to every new project.

  7. Don't use catalogue removal as a workaround 9:41

    Removing an asset from the Tableau catalogue doesn't just detach it from the project — it deletes the asset reference entirely, breaking anything connected to it. This is not a safe way to move an asset back out and shouldn't be treated as an undo button.

Worth Knowing
  • Removing an asset from the catalogue is destructive: it deletes the reference outright rather than just relocating it, breaking any dependent content.
  • There's no documented way to move an asset back out of a project once moved in, other than potentially the default folder, which Tim considers a poor fit since it would attach to every project.
  • The permissions window's layout genuinely changes depending on whether an asset is locked to a database or has been moved into a project, which is easy to miss and confused Tim himself for a while.
  • Data lineage for a moved asset can look messy if the same tables are reused multiple times within a virtual connection.
Use It When

Reach for this when you want a database or table's access managed centrally through a project's permissions rather than its own, native database permissions — but be cautious, since reversing the move isn't straightforward yet.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.