Destination Hunts
Library & Shared Assets

Library & Shared Assets

How reusable content works in Destination Hunts — org-owned libraries, public shared content, visibility rules, and how library content is copied into events.

Everything reusable in Destination Hunts lives in the Management libraries in the sidebar:

  • Challenge Library — reusable challenges (with tags, a greater area, and an optional voiceover)
  • Artifact Library — power-up artifacts (freeze, steal, shield, …)
  • Collectible Library — collectible items that challenges can award or require
  • Game Templates — complete, reusable hunt blueprints
  • Greater Areas — the platform-wide city/region records that organize location content

Org-owned vs shared content

Library challenges and game templates belong to the organization that created them and carry a Visibility setting with three values:

  • Private (the default) — visible only to your organization.
  • Unlisted — an intermediate value available in the visibility select; in list views today it behaves like private for other organizations.
  • Public — shared globally: every organization sees it alongside their own content.

List views show your org's content plus public content — that's the whole sharing model. There is no separate "global library"; global content is simply content published as public.

Who can publish public content

Only internal (Destination Tours) organizations can set visibility to public. Anyone else attempting it is refused with "Only internal organizations can set visibility to public." This is how the shared global catalog is curated: Destination Tours publishes it, and every customer organization can see and clone it.

Library content is copied, not linked

When an event is created, its challenges are copies (snapshots) of the library content — not live references. Editing a library challenge later does not change any event that already includes it; a running hunt never shifts underneath its players. The same applies to challenge locations, which follow a three-layer snapshot hierarchy — see Greater Areas & the Location Hierarchy.

The one live layer is the template: a template links library challenges (with optional per-template overrides), and those links stay live until the moment an event is created from them.

Deep dives

On this page