In-App Messaging
En resumen
In-App Messaging is the conversation layer that lives inside Petanque Life — direct messages between players and officials, group threads for teams, clubs, and commissions, and broadcast announcements from federations to all members. Read receipts, file sharing with virus scanning, full-text message search, and tight integration with notification preferences keep coordination inside the platform instead of scattered across WhatsApp groups, missed emails, and noticeboards.
Cómo funciona
Every authenticated user has a messaging inbox keyed to their player profile and roles. Direct messaging supports any-to-any conversations within a tenant — player to player, official to player, coach to athlete — with per-tenant policy gates that can restrict who may initiate (for example, only licensed members in good standing can DM officials).
Group messaging spins up automatically around platform objects: every team gets a team thread, every club gets a members thread, every commission gets a working thread. Membership tracks the underlying object, so adding a player to a squad adds them to the squad's group, and removing a coach revokes thread access at the same instant. Federation announcements are a one-to-many flavour: a communications officer composes once, picks a segment (all members, license holders only, age category, region), and the message lands in every recipient's inbox plus their preferred notification channel.
Message read receipts are timestamped per recipient, so a referee can see whether the players acknowledged the court change. File sharing accepts photos, scoresheets, PDFs, and short clips up to per-tenant limits, with virus scanning before the file becomes downloadable. Attachments inherit conversation permissions — they cannot be hot-linked outside the thread.
Message search runs full-text over the user's accessible threads, filtered by sender, date range, and attachment type. Conversations are stored with end-to-server encryption, deletion respects the federation's retention policy, and every message can be reported for safeguarding review (linking into F17). Push and email fall-back is delegated to the Notification System, so users with quiet hours configured will see a digest rather than a 22:00 ping.
Capacidades clave
- Direct player-to-player and official-to-player conversations
- Auto-managed group threads for teams, clubs, and commissions
- Federation-wide broadcast announcements to filtered segments
- Read receipts with per-recipient timestamps
- File sharing with virus scanning and per-tenant size limits
- Full-text search across all accessible conversations
- Integrated with notification preferences and safeguarding reports
En la práctica
Two hours before a league fixture, a club captain opens the team thread, posts the latest weather forecast, and attaches the start list as a PDF. Read receipts show six of seven players have seen it; he taps the seventh player's name and switches to a direct message to confirm by SMS. Mid-match the referee uses the official-to-player feature to message both captains a court reassignment; the message lands as a push notification within seconds.
Two days later the federation sends a broadcast announcement about an upcoming course; it appears in every licensed member's inbox, segmented by region, and read receipts let the federation see uptake before sending a follow-up.
Funcionalidades de este subsistema
6| ID | Status | Funcionalidades |
|---|---|---|
| F09.03.01 | Entregado | Direct messaging (player to player, official to player) ✅ PL-F0903 |
| F09.03.02 | Entregado | Group messaging (team, club, commission) ✅ PL-F0903 |
| F09.03.03 | Entregado | Federation announcements (broadcast to all members) ✅ PL-F0903 |
| F09.03.04 | Entregado | Message read receipts ✅ PL-F0903 |
| F09.03.05 | Entregado | File sharing in messages ✅ PL-F0903 |
| F09.03.06 | Entregado | Message search ✅ PL-F0903 |
Partes interesadas que necesitan este subsistema
Aparece en 7 análisis de partes interesadas