How organizations, programs and teams fit together

Everything nests strictly downward, with no exceptions and no shortcuts between levels.

• Organization, the club itself. Crestview Community Sports Alliance.
• Program, one season of one sport. Fall 2026 Youth Basketball.
• Team, one roster inside that season. The Raptors.
• Roster, the people on that team. Players, coaches, managers.

A team always belongs to a program, and a program always belongs to an organization. There is no way to make a team that floats on its own, which is deliberate: a team with no season attached has nowhere to keep its fees, its registration form or its dates.

If you take one thing from this page, take this. The program is not paperwork sitting between your club and your teams. It is the thing that holds the money.

A program owns the registration fee, the form families fill in, the add-ons, the discount codes, the capacity limit and the age range. Registration happens against a program, payments belong to a program, and your financial reporting is per program.

The practical consequence: when you want to change what something costs, what the form asks, or who is allowed to sign up, you are looking for the program. Not the organization, and not the team.

The organization is deliberately thin. It carries your name, your logo, your location, your staff, your documents and your payment connection, and that is close to all.

In particular it does not carry a sport. One organization can run baseball, softball, tennis and football at the same time, so the sport belongs to the program. A club that added a second sport and found itself needing a second account would be a badly designed product.

See organization settings for what it does carry, and who can do what for how access works across the four levels.

In order, because each one needs the level above it to exist first.

• You create the organization once, and most people never create a second.
• You create a program at the start of each season.
• Teams come either from you creating them directly, or from a league program where players register first and you split them into teams afterward.
• Rosters fill from registrations, from a draft, or by adding somebody manually.

See setting up your first season for that path end to end.

A parent whose child plays on two teams has one account and two roster entries. A coach who also has a child in the league is a coach on one roster and a parent on another, from the same login. Nobody needs a second account, and creating one causes more problems than it solves.

See which account type to choose for the account side, and team staff permissions for what a team role actually unlocks.

When you cannot find a setting, this is usually the fastest way to work out where to look.

• Organization: name, logo, location, staff and volunteers, admins, documents and waivers, your Stripe connection, your plan.
• Program: the fee, the registration form, add-ons, discount codes, capacity, age limits, and whether snacks and carpools appear.
• Team: the schedule, the roster, the message board, chat, volunteer jobs, the team's own site.
• Roster: one person's place on one team, including their role and permissions there.

With the model in place, the setup path makes a lot more sense. See how to set up your first season.