Video | Tableau | Data visualisation | Tool strategy

How to use Collections: New in Tableau 2021.2

Collections are like tags, but monumentally better, giving every analyst their own curated corner of Tableau Server.

Part ofWhat's new in Tableau 2021.2
Watch on YouTube
  • Collections get their own dedicated space on the left of Tableau Server and are private by default, so the creator must explicitly share them before others can see them.
  • Think of Collections as a much better version of tags: you bring content from across the server into one curated space, and a single item can sit in multiple collections at once.
  • You add content by browsing the Explore tab and using the actions menu or three-dot menu; most asset types work, but lenses can't be added and draft Prep flows are excluded.
  • Sharing a collection sends a link and then prompts a permissions window, but Collections never override the underlying permissions model, so users only see items they already have access to.
  • You can change a collection's owner to hand over stewardship, and deleting a collection removes the collection only while leaving all the underlying content untouched.

Collections, released in Tableau 2021.2, let each analyst curate their own personal corner of content pulled from across Tableau Server, working like a much smarter, more flexible version of tags.

Collections had been in public beta before landing officially in 2021.2 with feedback baked in. The video walks through finding, creating, populating, sharing and eventually deleting a collection.

The Breakdown
  1. Find and create a collection 0:40

    Collections get a dedicated space on the left-hand navigation of Tableau Server, separate from the usual project/content browsing. Creating one is a single click and it's named after you and set to private by default, giving you your own customisable corner of the server rather than a one-size-fits-all view.

  2. Add a description to frame its purpose 2:02

    Once created, you can edit a collection's description to state what it's for; this is worth doing deliberately since it's the main signal to others about what belongs there and why.

  3. Add content via the Explore tab 2:24

    You don't add content from within the collection itself — instead you browse Explore (the standard server content browser), select items, and use the actions or three-dot menu to add them to a new or existing collection. A single item can be added to multiple collections at once, which is useful for something important that different audiences need to find via different links.

  4. Know what can and can't be added 4:41

    Most asset types — projects, workbooks, data sources, finished flows, metrics — can go into a collection, but lenses cannot, and Prep flows still in draft are excluded; only finished flows work.

  5. Remove content just as easily 7:50

    Removing an item from a collection is done the same way, via the actions menu, and takes effect instantly with no extra confirmation step.

  6. Share and manage permissions 8:12

    Because a collection is private until you explicitly share it, sharing sends a link and then automatically prompts a permissions window so you can grant view access. Collections never override the underlying permissions on the content itself — if someone doesn't have access to an item, adding it to a collection they can see doesn't reveal it to them, so you can safely share one collection link with a mixed group and let each person's existing permissions determine what they actually see.

  7. Hand over ownership or delete 11:12

    You can change a collection's owner to pass on stewardship, useful when someone moves roles. Deleting a collection is described as fairly drastic to do carelessly, but it only removes the collection itself — all underlying content stays exactly where it was, even if it belonged to multiple collections.

Worth Knowing
  • Lenses can never be added to a collection, and Prep flows must be finished (not draft) to be added.
  • Collections are private by default, so nobody else will see one until you actively share it and grant permissions.
  • Sharing a collection only sends a link — you still need to grant permission in the follow-up window for the recipient to actually view it.
  • At the time of recording there's no way to customise the layout of a collection (e.g. arranging metrics and dashboards together) beyond plain list or grid view.
Use It When

Reach for Collections when you want a single, shareable, curated view of content scattered across projects and asset types — for example a business-area hub where different teams see the same collection link but only the specific workbooks their existing permissions allow.

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.