What your team site shows the public

That is a decision rather than an omission. A roster block did exist once and was removed, along with every other page that published children by default, because a list of children's names, ages and photographs on a page anybody can reach is the single worst thing a youth sports product can ship.

If you want families to see a roster, they already can, once signed in. The public site is for people who are not in your organization yet.

The Coaching Staff block is the only one that publishes people, and it publishes only adults in a staff role: coaches, managers and volunteers. Never players.

For each one it shows a name, the role, a custom title if you set one, and their profile picture. It does not publish an email address or a phone number, which is the detail worth knowing before you worry about it.

Taking somebody off it

Each staff member has a visibility setting on the roster. Turn it off and they stop appearing on the public site while staying on the team exactly as before.

See managing your roster.

Schedule is the only other block that reads live team data, and it is deliberately narrow: upcoming events only, with the title, the type, the date, the time and the location. No attendance, no RSVPs, nobody's name.

Standings publishes a win, loss and tie record and nothing about individuals. Those numbers are typed into the builder rather than counted from your results, so nothing about a game reaches the page unless you put it there.

The remaining blocks carry no live data at all. Text, images, videos, news, sponsors and so on show exactly what you put in them, which means the main risk on a team website is not the software but what somebody pastes into a text block.

The photo gallery block is worth naming specifically, because it is easy to assume it mirrors your team photo albums. It does not. It shows only the images you place in that block by hand, so nothing from a private album reaches a public page by accident. See team photo galleries.

If you are putting photographs of children on a public page deliberately, the consent question applies with more force than it does inside the app. See photos of children and consent.

A site sits unpublished until you say otherwise, and a visitor reaching it before then gets a "Coming Soon" page rather than a half-built one. You can preview it yourself at any time while it is still private.

Unpublishing takes it straight back to that state, which is the right move if something goes on the site that should not have.

See building a team website.