Teams versus creator pages

Events belong to teams. Public directories exist for both the team and the person who created the event. Those are different URLs with different jobs.

Teams own the work

When you create a sign-up you do it from a team context, such as /settings/{teamId}/signups/create. Locations, slot templates, and the roster live there. Invite teammates if more than one person should edit dates or remove registrations.

A school PTA, a youth sports club, and a volunteer fire company should each be a team. One person can belong to several teams. Do not dump unrelated events into a single team just because you are the one typing them in.

The public team page

/signups/team/{teamId} lists sign-ups for that team that have public listing turned on. It is the right link to put on a club website: visitors see current events without an account. Private events never appear there.

The public creator page

/signups/creator/{creatorId} lists publicly listed sign-ups created by one user, across teams. That helps when people know you, not the organization name. It is not a replacement for the team page. If you leave a team, treat that creator page as a personal directory, not the club’s official calendar.

Search

Search looks across publicly listed events by title or organizer email. It will not return private events. If someone cannot find your event in Search, check the public listing checkbox before assuming Search is broken.

Who should get which link

• Parents who follow the school: team page
• A friend who only knows your email: creator page or Search
• A closed staff list: direct event URL, listing off

Ads on public event pages, when they are shown at all, follow the owning team’s plan, not the visitor’s account. Attendees do not need to subscribe to register.