Organisation
Affiliations
Invite independent clubs to join the federation. An affiliation requires both the federation and the club to say yes — and records consent and placement, not data migration.
🔗 Propose club affiliation
Invite an independent club to join the federation. The club is placed under a node in your structure and must itself consent via a one-time link before the affiliation is recorded.
Next step: the case appears in Cases where the federation approves, and the club admin consents via a one-time link.
🔗 Propose club affiliation
✓ Case created. Manage it under Cases and invite the club admin to consent.
🔗 Propose club affiliation
The selected placement cannot hold a club — choose a node (e.g. district/comité) that may have clubs beneath it.
Not available
This section is not available for your account.
The migration moves the club's documents to the federation tenant and puts the source in read-only mode. The club admin consents via a one-time link before anything is moved.
| Dataset | Document count | Conflicts | Action |
|---|---|---|---|
| Memberships | 312 | — | Moved |
| Licences | 298 | 2 (licence number clashes) | Renumber |
| Matches & results | 4,815 | — | Moved |
| Club code | 1 | 1 (code NORDVIK taken) | Change code |
| Calendar events | 77 | — | Moved |
The preview counts documents per dataset and detects clashes (licence numbers, club code) before anything is written.
Rollback window
Migrated 2026-06-20 · 22 days left of the rollback window. The undo button moves all migrated documents back and lifts the source's read-only mode.
Conflict handling & execution
✓ Consent confirmed by the club admin 2026-06-18 (one-time link).
Execution moves the documents, repoints them to the federation tenant and puts the source tenant in read-only mode until the rollback window closes.