Prepare the federation hierarchy, season, affiliations, fees, required forms and club access before inviting clubs to submit members. Setup determines what clubs can request, who can manage those requests and what processing can create.
The main federation manages shared seasons and affiliation definitions. Participating federation organizations configure their own attached fees and requirements. Club representatives can use the federation’s client portal; some clubs instead use their own Activity Messenger administration workspace.
Your organization must have federation access and the appropriate administration permissions. Seeing a branch in the overview does not grant unrestricted editing or billing access to that branch.
An affiliation connects a member to a club for a season. A billing item defines an organization’s fee, taxes and optional linked membership. An affiliation request is submitted information awaiting processing or review. The resulting affiliation, membership, invoice and payment are related records with separate statuses.
Participating organizations work with this shared season and save their own configuration. Season dates also influence the initial activation and expiry of linked memberships during processing; non-expiring memberships are handled separately.
Use clear names such as recreational and competitive. Shared names and categories belong to the main federation; participating organizations attach their own fees and form requirements. Changing a definition is not a substitute for adjusting a member’s existing affiliation or invoice.
The example below shows a participating federation: shared identity fields are read-only here. Edit those fields in the main federation.
In the federation billing-item editor, create each organization’s fees:
When attaching an item, review its price override, age conditions and region where available. A blank override uses the billing item’s default price. Check which organization owns each fee: fees at different hierarchy levels can result in different invoices.
A member may hold the same affiliation in several clubs while sharing a linked membership. A membership granted once does not mean every fee is charged only once. Review the actual fee configuration and processing results.
For upgrades, check the starting affiliation, the added affiliation and any dependent discounts. Later cancellation of the starting affiliation can remove a discount and change the net credit; administrators must review the invoice-impact preview.
Normal activation depends on satisfying the configured requirements. Submitting a form and satisfying its approval condition are not always the same thing. Processing or paying an invoice does not prove that a missing form has been completed.
In the season’s Configuration → Club/Program area:
The client portal access path requires the access form, club key and approval mapping. A representative’s matching access submission must be approved. If a club cannot see the season, check these mappings and the representative’s approved response before changing unrelated member data.
In the same configuration area, select Forms available to clubs for import. Eligible forms contain an affiliation question connected to this season. Enable import where required; payment forms cannot be imported through the client portal.
Add season instructions in both languages. Explain which form to use and whom to contact. Then choose which club actions to allow:
Grant these according to the club’s role. A club that can import forms does not necessarily have permission to process affiliations or merge records. Verify the resulting portal rather than assuming every administrative control will appear there.
Under Configuration, review Payment options and Member fields where available. Select the permitted invoice payment methods, confirmation template, administrator notifications and the profile fields used when updating members. Ensure the billing contact and organization issuing each fee are appropriate.
The form-import dialog states that imported respondents do not receive a confirmation email. Do not confuse import notifications with the separate invoice confirmation settings.
Walk through one approved demo club and member: correct season access, available form, affiliation choices, age/region eligibility, fees and taxes, linked memberships, required forms and billing contact. Review both languages and each organization’s fee ownership.
Keep four outcomes separate: a submitted request, a processed affiliation, completed requirements and a paid invoice. Use the member record and invoice to verify each outcome.
Review season dates, affiliations, fee prices, form mappings, portal permissions and payment settings for the next period. The main federation has season lifecycle controls, including archived-season access and restoration. Review any duplicated setup before clubs use it; do not assume old dates, forms or prices are still correct.