A registration form is built from four things: the fields you ask, the packages you sell, the rules that decide who's eligible, and the settings that control when and to whom it's open. This is a tour of what's possible, not a step-by-step — for that, see Create a registration form.
Fields
Every question on a registration form is added from Add question in the builder, as either a default field or a custom question.
Default field — pulls from two sources at once: 360Player's built-in contact fields (name, email, date of birth, phone number, address, gender, nationality, and similar) and any custom questions your club has already created and saved on other registration forms. Picking one keeps the question reusable across registrations.
Custom question — creates a brand-new question just for this registration, in whatever answer type you need: short text, single choice, multi-choice, date, file attachment, and more.
Mark any field Required to make it mandatory. Required Date, Single choice, and Multi-choice fields are also the only fields that can drive field-based package eligibility, below.
Packages
Packages bundle a product, a payment option, and an eligibility rule into one purchasable option, so a single registration can offer different prices or age groups without separate registrations. A package needs only a name and description — products, payment, and eligibility are all optional layers on top.
Products — one or more products to charge for, each with its own validity dates, quantity limits, tax rate, whether the registrant can adjust the quantity, and whether it's required or optional within the package.
Payment options — how a product gets paid for:
Upfront — one payment in full.
Installment — split across a set number of payments.
Subscription — a recurring charge on an interval.
Package managers — users granted permission to view submissions to that specific package and help manage team assignments and invitations. If the package is connected to a team-invitation registration, a package manager can only assign players and send invitations for teams they already coach or manage.
Custom email — a package-specific confirmation email that replaces the registration's general submission email for registrants of that package. It only sends if Send email upon submission is turned on at the registration level — the package's own toggle alone doesn't send anything.
Eligibility rules
Each package uses exactly one eligibility mode:
Open package — anyone can register.
Field-based rules — access depends on how the registrant answers a field on the registration. Only required fields of type Date, Single choice, or Multi-choice can be used this way. Add multiple rules and the registrant must meet all of them to be eligible.
Team invitation — only players who've been sent an invitation can access and register for the package. See Team invitation settings below.
Field-based rules and team invitation can't be combined on the same package — turning on one removes the other as an option.
Team connections
A team connection automatically places anyone who registers through that package onto a specific team once they submit.
Pair it with an eligibility rule to control who can reach the package in the first place — without one, the package, and its team connection, is visible to everyone.
A package can't use both a team connection and team-invitation eligibility. Use a team connection for open or field-based packages, and team invitation for invite-driven placement instead.
Team invitation settings
Team invitation settings connect this registration to an earlier one — a tryout or interest registration, for example — so you can invite specific respondents to specific teams instead of leaving a package open to everyone. Click Connect player pool to pick the earlier registration as your source of players, then assign players to teams and send invitations tied to packages that use team-invitation eligibility. When an invited player accepts, submits, and pays, they're placed on the matching team automatically.
At least one package needs Eligibility: Team invitation with a team connection before Connect player pool has anywhere to invite people into.
Visibility
Public — listed on your public form site and in the club lobby, open to anyone.
Club lobby — visible only to members of your organization.
Unlisted — hidden from both; reachable only by sharing the direct link.
Availability
Limit responses — closes the registration automatically once a set number of submissions is reached.
Limit to one submission per user — blocks a second submission from the same account. Since it's enforced per account, it needs Require a 360Player account turned on too — without an account tying submissions together, the same person can still submit more than once as a guest.
Schedule registration — set the registration to open and close automatically at specific times.
Invite only — restricts submissions to people who've been sent an invitation.
Require a 360Player account — registrants must log in or create an account before they can submit.
Separate from all of the above, the registration's status — Open, Closed, or Draft — is the master switch: Draft is preview-only, Closed blocks new submissions outright, and Open is what makes the availability settings above matter.
Submission email
Turn on Send email upon submission to have 360Player email registrants a confirmation automatically, and customize its subject and content, or leave the default. A package's own custom email, above, takes over for registrants of that package specifically — but only once this registration-level toggle is on.