Greater Areas & the Location Hierarchy
Platform-wide city/region records, how library challenges are scoped to an area, and the three-layer library → template → event location hierarchy.
What a greater area is
A greater area is a platform-wide city or region record (for example, "Boston"). Greater areas are not org-scoped — they are managed internally by Destination Tours and shared across the whole platform. Each one has a name, a unique slug, an optional color, and a sort order. They're managed under Greater Areas in the sidebar's Management group.
How challenges are scoped to an area
A library challenge belongs to at most one greater area, set via the Greater Area dropdown in the challenge editor's Location section (library challenges only — the dropdown's description reads "The city or region this challenge belongs to").
A challenge with no greater area is global/unscoped: it appears regardless of which area is selected in an area filter. A challenge assigned to an area narrows to that city.
Where the area filter surfaces today
- Challenge Library — Map view: the map editor has a Select greater area dropdown that scopes the map to one area.
- Challenge Library — List view: the list shows a greater-area column, but list filters are currently disabled — only search and column sorting are active. Area filtering is a Map-view feature for now.
The three-layer location hierarchy
Challenge coordinates flow through three layers, each overriding the one below it:
- Library challenge latitude/longitude — the base, and it is live: editing it moves the pin everywhere that still inherits it.
- Template link override — each template's link to a library challenge carries its own nullable latitude/longitude. When set, it overrides the library pin for that template; when null, the template inherits the library location. This layer is also live: the resolved template pin is the link's coordinates if set, otherwise the library challenge's.
- Event challenge snapshot — when an event is created, the resolved location (template override or library base) is frozen onto the event challenge. From then on it is independently editable, and later edits to the template or library never move a running event's pins.
Which edit surface writes to which layer
| Where you edit | Layer written |
|---|---|
| Challenge Library editor / library Map view pin drag | Library challenge (base, live) |
| Template's challenge list pin edit | Template link override (live for that template) |
| Event's Challenges tab / event Map editor | Event challenge snapshot (that event only) |
Rule of thumb
Fix a wrong address in the Challenge Library and every template and future event inherits the fix. Nudge a pin on an event and only that event changes — existing events are never touched by library or template edits.
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.
Game Templates
Reusable hunt blueprints — what a template captures, visibility and cloning rules, saving an event as a template, and how events are created from templates.