A tracker represents one reporting device configuration. It has a short identifier (TID), an access token, and can publish location data to Drup Trails through the API endpoint.

• Use one tracker per physical device or use-case for cleaner history.
• The access token acts like a password for publishing reports.
• You can update the tracker identifier later if needed.

A team is a collaboration boundary. Members of that team can access data from trackers attached to the team based on team permissions.

• Attach one tracker to multiple teams when sharing is intentional.
• Detach trackers from teams to limit visibility without deleting the tracker.
• Keep team membership current to reduce unnecessary exposure of location data.