Communication and coach tasks

Two different coordination tools

Conversations are for authorised discussion. Tasks are for explicit work with an assignee and state. Using them for their separate purposes helps an institution distinguish “we discussed it” from “someone is responsible for completing it”. This is a workflow benefit, not a measured reduction in administrative time.

Direct and group conversations

In Messages, staff choose an authorised person from the people list to open or resume a conversation. Existing direct conversations are reused rather than creating a new thread for each contact. Athletes can read and reply to conversations started by staff within their permitted scope.

A training group can open its linked shared conversation. Reopening it returns to the same group conversation. Review the visible participant list before sharing: a group discussion has a different audience from a private pair.

Two-person conversations remain participant-private; a nonparticipant administrator cannot simply read or join them. Group membership is explicit and administrators may join supported group conversations visibly. Institution administration does not imply blanket permission to inspect private messages.

Files and notifications

Where the application permits an attachment, its access follows the authorised conversation and resource rules. Exercise resources and private conversation files are different collections. Use only permitted demonstration material, and never send health details or private files through this public website’s contact form.

Multiple attachments in updated installations

The web composer supports up to 10 attachments per message, up to 25 MB per file: PNG, JPEG, WebP, GIF, MP4 and PDF. Use the photo or paperclip button to select several files, review their previews above the input, and remove any file before sending.

Successful sends clear the attachment list. Failed or uncertain sends retain the draft for recovery. If a batch upload stops partway through, earlier successful uploads remain attached; choose the failed and remaining files to continue. Conversation membership still controls access, and unsent uploads remain private to their uploader.

This update requires the corresponding frontend/backend changes and migration 202610181200_message_attachments. Existing single-file messages remain readable. Sent messages now show each attachment's file name, and documents download with their original names.

Focused browser checks in Chromium desktop and WebKit phone emulation covered several files, removal, reload, a lost acknowledgment followed by an exact retry, and the recipient losing file access after deactivation (application PR #130). These checks are not physical-device evidence. See the API reference for asset_ids, attachments and compatibility details. This web messaging API is outside the coach field OpenAPI subset.

The notification bell and preferences help members return to authorised activity. A notification link still checks current access. In-app notification behaviour is not proof of external email, SMS, push or background delivery; do not rely on an unconfigured external channel for urgent institutional processes.

Assign a coach task

An administrator can create or update a trainer task with a title, description, assigned active trainer, priority and optional due date. Trainers see their own assigned queue and can complete or reopen their work. Administrators can reassign work and manage cancellation/restoration through the allowed workflow.

Use a concrete task such as “Review the recorded assessment results” and name the responsible coach. A task is not a training prescription and does not replace a scheduled event. Due dates should represent an agreed operational expectation, not an automatically inferred athlete-risk score.

Follow up on actual pending work

The institution follow-up view draws from records such as training awaiting review, past bookings awaiting an outcome and athletes without an active assignment. These are useful places to check whether a workflow needs attention. A missing outcome is not automatically a no-show, and a missing assignment is not evidence of poor coaching.

For a handover, review the queue, update coach responsibility and reassign explicit tasks where needed. Current membership and assignment checks apply even to a retried request; a former assignee must not retain access merely because an old tab is still open.

Example evaluation

Create a synthetic task, complete and reopen it, then reassign it to another coach. Confirm the former assignee no longer has the same authority. Open a group conversation and a private pair, and verify their visible membership and access rules separately.

Continue with administration, roles and analytics. Sensitive incident reporting and emergencies require institution-approved processes outside an unverified notification channel.

Source and scope

Reviewed against current institution-scoped API contracts on 17 October 2026. These are workflow capabilities, not a claim of completed university or production acceptance.

API reference