Name, title, and public route
Teams have both an immutable name and a mutable title. The name is the compact route-safe identifier used in URLs such as
/{culture}/team/{team-name}. The title is the human-facing label people see across the UI and can update later.
This separation keeps links stable while letting the team adjust branding and display copy over time.
Team page visibility and join policy
A team page can be public or team-member-only. The page visibility controls who can open the route itself. Join policy controls whether public requests are allowed or whether the team stays invite-only.
- Public team pages can appear in the public team directory and on public search or sitemap surfaces.
- Member-only team pages can still exist, still have notes, and still power team workflows without being publicly browseable.
- Requests from a public team page still wait for admin approval.
- Invite links and team-admin actions remain separate from the public page itself.
Admins and members
Teams are not flat lists of people. Admins and members have different powers. Admins can manage page settings, approve requests, create and revoke invite links, run team exports, and delete the team. Members can still participate in team notes and may hold item-specific powers on trackables they activated for the team.
How teams relate to notes
Team notes are notes with a team association layered on top of the underlying user ownership. That combination is what allows moderation, deletion fallbacks, public/team-private visibility, and author-aware behavior to coexist.
- A team note can be private to the team or public to everyone, depending on the chosen visibility.
- Comment policy for team notes can allow anyone logged in, only team members, or no comments.
- Team categories define the hierarchy for team notes and are managed separately from personal categories.
How teams relate to trackables
A team can own trackables and trackable groups. When a trackable is activated to a team, the team becomes the ownership scope. Team admins can manage it, and the activating member keeps management authority while they remain on that team.
- Team ownership is different from the original creator of the item.
- A team-owned trackable can appear on public or private trackable pages depending on the trackable visibility rules.
- If the activating member leaves the team, they lose team-based access even if they were once the activating person.
- If the team is deleted, the product can fall back to a user-based ownership path instead of simply destroying surviving shared history.
Team exports and deletion
Team exports are admin-only because they include shared records that belong to the group, not just to one member. Team deletion is also an admin-only action because it can convert notes, detach trackables from the team scope, and remove team-wide joins, categories, and access grants.
- Deleting a team is not the same as deleting a member account.
- Team-wide data may survive a member leaving or deleting an account.
- Trackable secret credentials are withheld from ordinary team exports unless a deleted or unavailable user owner makes recovery necessary.