What the group owns
- A group has its own title and description.
- A group can define a default item title and default item description.
- A group can define one verified default external link for grouped items that intentionally keep using it.
- A group can be personal or scoped to a team.
What stays item-specific
The group does not replace the trackables inside it. Each item still has its own public code, secret code, private scan URL, activation state, ownership scope, comments, and journey history.
Trackable groups can provide fallback item title, description, and default link values while the group page shows which items are still waiting for activation.
- Activation happens per item, not once for the whole group.
- A group page can show that some items are activated while others are still waiting.
- Grouped items can link to their managed item page and, when public, their canonical public page.
Defaults and fallback behavior
Group defaults are only fallbacks. They are used when the item-level metadata is intentionally blank and the product rules still allow fallback for that item.
- Unactivated handoff items commonly start with placeholders such as Unactivated Trackable and Please activate this trackable item.
- During activation, the owner can either save an explicit item title and description or intentionally copy the group's current default wording into the item.
- If an activated item should stop inheriting the group wording, save the item's own title and description instead.
- If an activated item should keep the group's verified default link, that choice is explicit during activation.
If you create a group without activating every item immediately, you can also keep the group on your watch list so later activations, comments, and secret-code access still reach you as a follower.
If one of those grouped items later belongs to you too, LocationNotes merges the owner and group-watch delivery choices for that event instead of sending duplicates.
Viewing a group page
Trackable groups now have two page layers: a shareable group page for public or authorized viewing, and a separate signed-in workspace dashboard for management.
Share the public group URL family as /trackable-group/{publicCode} and the browser can land on /{lang}/trackable-group/{publicCode} after localization. The signed-in management dashboard remains the place where owners and team members manage defaults, activation progress, and private workflow details.
The easiest mental model is Visible Once Accessed versus Always Visible To Everyone. An Always Visible To Everyone group page can be shared broadly. A Visible Once Accessed group page can still stay reopenable for a signed-in account after that account unlocks one of the group's member trackables through the secret code or QR flow.
The saved stop is an immutable logistics snapshot. If a linked note later moves, the journey keeps the original snapped coordinate so the route history does not silently change.
Trackable read models can also surface the current visible notes at that coordinate, so the route can stay accurate even when nearby notes later change.
Place, history, and access stay separate: the journey stop preserves the snapped coordinate, the note keeps its own editable record, and the note's visibility plus required access scope decides who can open note content.
The website's public trackable-group list stays multilingual for the same reason as the public trackable list: shared journey and inventory context should not disappear when groups span authored languages.
Switch the website language when you want localized chrome around the same public trackable data.
Group dashboards and grouped-member rows also show last activity so the most recently touched inventory stays easy to spot.
- Each member row can show whether the item is activated.
- Each member row can link to the managed or Visible Once Accessed trackable page.
- When a member trackable is public, the row can also link to its public page.
- Owner or team links may also appear when that related page is available to the current viewer.
Editing and regrouping
Editing a group changes the group's identity and defaults going forward. It does not silently overwrite every item with copied metadata.
- A trackable can belong to only one group at a time.
- Moving a trackable to a different group is a detach-first workflow. Remove it from the old group first, then reassociate it to a new one later.
- Group edit access follows the documented ownership and team-admin rules.