The short rule
Share only the public URL family for the thing you want someone else to open. Do not share management URLs, edit URLs, owner-scoped internal URLs, or secret-code URLs. Public URLs are for project handoffs, email, QR labels, screenshots, printed materials, and search indexing.
A public URL should only be copied when the page or item is publicly reachable in its current state. A private note, a note already gated by associated-trackable access, a private team page, a Visible Once Accessed trackable, a Visible Once Accessed trackable group, or an internal management screen should never be copied as the public address.
Public URL families
Use the short share URL when you copy a public link into email, posts, QR labels, or printed material. The localized landing column shows the page shell people may see after the browser applies the viewer's language or opens the localized route family directly.
Profile page URLs and visibility
Share the public profile with
/Profile/{userName}.
The user name is the stable route key for that page family, which keeps copied links compact and easy to recognize when someone is trying to open a person's public-facing page.
After the visitor opens it, the site can render the same public profile page inside a localized route shell such as
/{lang}/Profile/{userName}.
Profiles have three route-level visibility states. Private Profile means only the account owner can open the profile page. My Teams Are Allowed To View means the owner and signed-in people who share a current team with that user can open it. Public Profile means anyone can open the profile page URL directly.
This setting controls the profile route itself. It does not mean the user name disappears from every other place where that person is already allowed to appear, such as note ownership, team rosters, or trackable owner labels.
Team page URLs and visibility
Share the short team URL as
/team/{teamSlug}.
After the visitor opens it, the site can render the same public team page inside a localized route shell such as
/{lang}/team/{teamSlug}.
Team pages are either public or team-member-only. A public team page can be opened by anyone and can appear in public discovery surfaces. A non-public team page is still a valid working team page, but only signed-in current team members can open that route.
Join policy is related but separate. A team can be public and still require admin approval for requests, and invite links remain a different access path from the page visibility itself.
Note page URLs and visibility
Share public note pages with
/Note/{noteId}.
The browser can then land on the localized public page shell at
/{lang}/Note/{noteId}
while still opening the same note record.
Notes can be personal or team-scoped, and then public, private, or gated by associated-trackable access within those scopes. A public personal note can be opened by anyone. A private personal note stays restricted to the owner. A team note can be public to everyone or kept inside the team. A note using VisibleOnceAssociatedTrackableAccessed behaves like a public note until one or more trackables are attached to it. After that, the note page opens only for people who already unlocked one of the associated trackables.
Public note pages are separate from the source profile or team page. That means a note may still have its own public route while the profile page or team page it came from has narrower visibility. Notes that switch into associated-trackable gating also stop being publicly indexable once one or more trackables are attached.
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.
Current note access still follows the note's own visibility and required access scope, and journey reads can surface whatever notes are currently visible at the same coordinate without turning the stop into a permanent note owner.
Trackable page URLs and visibility
Trackables use one entry route for public codes, short secret codes, and long private scan tokens. Share
/trackable/{code},
and if the code is public the site can resolve that into the rendered public page at
/{lang}/trackable/{publicCode}.
Trackables can be Always Visible To Everyone or Visible Once Accessed regardless of whether they are personally owned or team-owned. Always Visible To Everyone trackables can be shared with the short /trackable/{code} URL and can be opened by anyone. Visible Once Accessed trackables stay off the public route, but the secret code or QR flow can still link the item to a signed-in account for later reopening on future signed-in devices.
Secret short codes and QR-only scan payloads are not public URLs. They are possession credentials. Once a signed-in account uses one successfully, that account can keep reopening the trackable on later signed-in devices without re-entering the secret. A team-owned trackable can still be Always Visible To Everyone, and a personally owned trackable can still be Visible Once Accessed. Ownership scope and page visibility are separate rules.
Trackable-group page URLs and visibility
Share Always Visible To Everyone group pages with
/trackable-group/{publicCode}.
The public group page can then render inside the localized shell at
/{lang}/trackable-group/{publicCode}.
Trackable-group pages also have a page-level visibility rule. An Always Visible To Everyone group page can be opened by anyone. A Visible Once Accessed group page stays limited to signed-in viewers who already have group access, including owner or team access and accounts that were previously linked through one of the group's member trackables.
Group visibility does not automatically force the same visibility on every member trackable. Each member trackable still keeps its own item-level visibility and may or may not have its own public page. A Visible Once Accessed member unlock can also keep the related group reopenable for that signed-in account later, so once you have access to the trackable you can reopen its group too.
Category URLs
Categories do not have their own separate public URL family. Personal categories live on the profile page at
/Profile/{userName},
and team categories live on the team page at
/team/{teamSlug}.
That keeps category sharing easy to explain: share the page that owns the hierarchy.
Category management happens on workspace pages instead:
/{lang}/notes
for a personal workspace and
/{lang}/team/{teamSlug}/workspace/Categories
for a team workspace. Those workspace URLs are signed-in management routes, not public-share URLs.
Why trackables keep the singular route name
Trackables keep the singular /trackable noun in both the share URL and the localized public page. The short share URL stays as /trackable/{code} because that one route can safely accept three different kinds of codes: the public code, the short secret code, and the long private scan token.
If the code is public, the browser is redirected into the viewer's language-specific public page at
/{lang}/trackable/{publicCode}.
If the code is secret or scan-only, the browser goes into the possession flow instead. That is why the short share URL is what people should copy, print, and email, while the localized rendered page is what visitors may end up viewing after redirect.
Why trackable groups use one public URL family
Trackable groups do not need a secret-code resolver, so the share URL and the localized rendered page stay in the same family:
/trackable-group/{publicCode}
localizes into
/{lang}/trackable-group/{publicCode}.
That means the group CTA can always teach one clean share format while the browser still lands on the viewer's language shell.
What should never be shared
- Internal workspace URLs such as /en-US/account or /en-US/team/{teamSlug}/workspace are management routes, not public-share URLs.
- Secret-code URLs and QR-only URLs are possession credentials, not public links.
- Management routes such as edit pages, team settings, activation pages, and internal dashboards are never public-share URLs.
Why this matters
People remember URL patterns. If the site teaches one simple family and then quietly routes people through internal one-off paths, they will copy the wrong thing into social posts, emails, labels, and support conversations. A clean public URL system reduces that confusion and makes the product easier to explain.
That matters even more when a link moves between coworkers, clients, professors, classmates, or printed field materials. Clear public URL families make shared notes and trackables easier to hand off without exposing the wrong page.
When the route is what matters, that same clarity helps support separate the saved stop snapshot from the note page itself and from any currently visible notes that happen to be shown at the same coordinate today.
Clear public URL families also make it easier to decide what is safe to share and what should stay private. When the public address is obvious, people are less likely to copy a management page, a private page, or a credential-based access URL by mistake.