← Back to all features
03
Membership & Licensing
63 features · 5 subsystems
Complete lifecycle management of player licenses, club memberships, federation affiliations, and inter-federation transfers. This is the backbone of the petanque administrative system.
License Management
F03.01 Planned
| ID | Status | Features |
|---|---|---|
| F03.01.01 | Planned | Configurable license types per tenant — each federation defines its own types (e.g., Sweden: 1 type; France: compétition, loisir, jeune, découverte). Each type has: competition eligibility, insurance inclusion, age limits, duration, renewability |
| F03.01.02 | Planned | License application workflow (club applies on behalf of player → federation reviews → approves → issues) |
| F03.01.03 | Planned | License numbering system (federation prefix + sequential, configurable format per tenant) |
| F03.01.04 | Planned | Annual license renewal (individual and bulk), season configurable per tenant (calendar year default) |
| F03.01.05 | Planned | Composite license fee calculation — fee = sum of configurable components (e.g., part fédérale + part ligue/region + part comité/district + assurance). Each component set at its OrgNode level. Supports regional price variation (France, Spain) |
| F03.01.06 | Planned | License card generation (digital + physical), with FIPJP symbol where required |
| F03.01.07 | Planned | License verification — QR code scan at events, public API for cross-tenant verification |
| F03.01.08 | Planned | License history tracking (all clubs, all federations, all years) |
| F03.01.09 | Planned | License suspension and revocation — only federation can decide (not club/district). Administrative fee configurable. |
| F03.01.10 | Planned | Time-limited license type — e.g., France's "licence découverte" (max 3 months, one-time only per player) |
| F03.01.11 | Planned | Grace period management for late renewals |
| F03.01.12 | Planned | Bulk license import from legacy systems |
| F03.01.13 | Platform | Audit trail on all license changes |
| F03.01.14 | Planned | One-license-per-nation-per-season enforcement (system-level constraint) |
| F03.01.15 | Planned | Season management (configurable per federation — calendar year, split year, etc.) |
| F03.01.16 | Planned | Medical certificate management — configurable per tenant: required at first license (France), renewal cycle (every 3 years), digital attestation sur l'honneur for annual renewal, upload/expiry tracking |
| F03.01.17 | Planned | License insurance declaration (licensförsäkran) — allows unlicensed player to participate if club has fulfilled obligations and player signs declaration (Sweden-specific but configurable) |
| F03.01.18 | Planned | International license issuance — member can request international license + health certificate for play abroad (required in France etc.) |
| F03.01.19 | Planned | Foreign license verification — player with foreign license can participate in national events by presenting valid license from issuing federation |
| F03.01.20 | Planned | Unauthorized player enforcement — configurable penalties per tenant (e.g., Sweden: 13-0 forfeit + 5000 SEK fine + exclusion from next year's equivalent event) |
Club Membership
F03.02 Platform+
| ID | Status | Features |
|---|---|---|
| F03.02.01 | Planned | Membership application (player applies to join club) |
| F03.02.02 | Planned | Club acceptance/rejection workflow |
| F03.02.03 | Planned | Membership categories — configurable per tenant (full, associate, honorary, youth, family, support, etc.) |
| F03.02.04 | Planned | Membership fee management per category |
| F03.02.05 | Planned | Membership card generation |
| F03.02.06 | Planned | Member directory per club (with privacy controls) |
| F03.02.07 | Planned | Membership start/end dates and status tracking |
| F03.02.08 | Planned | License club vs support membership — player has exactly one license club (competition rights) but can be support member in other clubs (no competition rights). System enforces single license club constraint. |
| F03.02.09 | Planned | Family membership grouping |
| F03.02.10 | Platform+ | Automatic membership renewal reminders |
| F03.02.11 | Planned | Club-bound competition enforcement — at club-bound events, system validates all team members hold license in the same club |
Transfers
F03.03 Planned
### Transfer Rules — Vary Per Nation
| ID | Status | Features |
|---|---|---|
| F03.03.01 | Planned | Intra-national club transfer (OrgNode change within same tenant) |
| F03.03.02 | Planned | International transfer (cross-tenant, nation to nation via public APIs) |
| F03.03.03 | Planned | Configurable transfer window per tenant — open period (Germany: Nov-Dec), free period before deadline (Sweden), or always open (Denmark). Tenant admin configures. |
| F03.03.04 | Planned | Configurable transfer approval workflow per tenant — who must approve (player, old club, new club, federation, district/region). Each step configurable. |
| F03.03.05 | Planned | Max transfers per season — configurable limit per tenant (Sweden: 2, others: unlimited) |
| F03.03.06 | Planned | Transfer quarantine during active league — configurable: player cannot transfer while league season is active (Denmark Landsturneringen) |
| F03.03.07 | Planned | Cross-region/cross-district transfer — additional approval required when transferring between OrgNode subtrees (Spain: autonomous federation approval, France: inter-comité mutation) |
| F03.03.08 | Planned | Outstanding obligations check — system blocks transfer if player has unpaid fees/active sanctions. Configurable blocking period (Sweden: max 2 years). |
| F03.03.09 | Planned | Carta de libertad / release letter — some nations require formal release document from departing club. Configurable per tenant. |
| F03.03.10 | Planned | ITC generation and verification via public API (peer-to-peer between tenants) |
| F03.03.11 | Planned | ITC workflow: player requests in new nation → new nation verifies license status via public API → sends ITC request → old nation reviews and approves/rejects → license marked "transferred out" → new nation issues license |
| F03.03.12 | Planned | Transfer fee handling — configurable per tenant (who pays, amount) |
| F03.03.13 | Planned | Transfer history per player (all clubs, all nations, all seasons) |
| F03.03.14 | Planned | One-nation-per-season validation on international transfer |
| F03.03.15 | Planned | Post-transfer competition eligibility delay — configurable per tenant (France: délai de carence ~30 days after mutation before player is competition-eligible in new club). Distinct from transfer quarantine (F03.03.06). |
| F03.03.16 | Planned | Transfer refusal appeal/escalation — when a step in the transfer workflow is rejected (e.g., old club refuses), player can escalate to higher OrgNode level (France: appeal to comité départemental). Configurable escalation path per tenant. |
| F03.03.17 | Planned | Transfer exception conditions — configurable per tenant: allow transfer outside normal window if specific conditions are met (Germany: Wohnsitzwechsel/residence change). Exception must be documented and approved by federation. |
| F03.03.18 | Planned | Multi-club membership toggle — configurable per tenant: some nations allow support membership in multiple clubs (Sweden), others forbid all multi-club affiliation (France: double appartenance interdit). |
| F03.03.19 | Platform | Audit trail on all transfers |
Federation Affiliation
F03.04 Planned
| ID | Status | Features |
|---|---|---|
| F03.04.01 | Planned | Club affiliation to regional/national federation |
| F03.04.02 | Planned | Annual affiliation renewal |
| F03.04.03 | Planned | Affiliation fee calculation (based on member count) |
| F03.04.04 | Planned | Affiliation document management (statutes, insurance proof, etc.) |
| F03.04.05 | Planned | New federation/club application process |
| F03.04.06 | Planned | Affiliation status (active, suspended, withdrawn) |
| F03.04.07 | Planned | Federation member count reporting (upward to parent) |
Insurance
F03.05 Planned
| ID | Status | Features |
|---|---|---|
| F03.05.01 | Planned | Insurance integration with license (mandatory liability) |
| F03.05.02 | Planned | Optional insurance add-ons (equipment, travel, accident) |
| F03.05.03 | Planned | Insurance certificate generation |
| F03.05.04 | Planned | Claim submission workflow |
| F03.05.05 | Planned | Insurance provider integration (API/file exchange) |
| F03.05.06 | Planned | Group insurance management for clubs/federations |
No features match your filters.