Teams keep shared trackables, mapped locations, and public group pages under adult-managed control for family, troop, school, and other group workflows.
Teams make ownership clearer when a family, troop, classroom, club, or other adult-led group needs shared access to the same pages and assets.
Use a team when more than one approved adult should be able to manage the same trackables, locations, categories, invite links, and public team page.
A public team page can explain the group and allow join requests. If the page is private, the join path falls back to invite-based access instead.
A team can own trackables, recent mapped locations, images, categories, and a verified outside link, all under one shared admin workflow.
The Register to and Place under choices let you keep something personal or move it into one of your current teams when it belongs to the shared mission.
A public team page can include the team description, public membership roster, public team-owned trackables, recent mapped team locations, uploaded team images, and one verified outside link when the team has chosen to publish one.
That page is also where join requests can start when the team is public and requests are enabled. Private teams stay limited to their invite and signed-in member workflows instead.
Public image galleries and public pages include reporting paths so visitors can flag inappropriate content, misleading claims, or links that should be reviewed.
If the problem is broader than one page, use the support page so the report can include the team slug, page URL, image details, or outside link that needs attention.
Use the create page when you need a new shared scope with its own title, description, public-page setting, join policy, images, and optional outside link.
Create TeamUse the signed-in teams page to jump into settings, invite members, create invite links, and open the team workspace.
Manage TeamsUse the public directory to discover recently active public teams, compare their public stats, and open the team detail page.
Find a TeamA team should help approved adults coordinate one shared mission. It should not be used as a workaround for giving independent accounts or unsupervised public presence to younger participants.
Families, teachers, troop leaders, and other organizers should decide which adults manage invite links, public pages, team-owned trackables, and content review before the team starts publishing widely.
Team-owned trackables and locations are part of the shared team workflow, so they should be treated as group assets instead of assuming they belong only to the person who happened to create the first draft.
That is why team admin permissions, join policies, and category management deserve clear setup from the start rather than being treated like optional cleanup later.
If a team is public, the page copy, join policy, external link, and published images should all match what the group is really comfortable sharing.
If something on the team page becomes outdated or inappropriate, use the support and reporting paths instead of letting the stale content keep circulating.
