Sessions in Lynk are always tied to a batch. This means the list of students you see inside any session is not manually created each time—it is derived directly from the batch roster.
This ensures consistency across attendance, notes, reports, and insights, while reducing operational overhead for coaches.
How the Session Student List Is Formed
When a session is created or opened:
Lynk pulls all active students from the associated batch
The list reflects the current roster status at the time of the session
Paused or ended students are excluded from future sessions automatically
This keeps session attendance accurate without extra setup.
Where Students Appear Inside a Session
Students appear in two key places within the session experience:
Attendance marking
When you open a session, all eligible students appear in the attendance list
Coaches can mark present, absent, or update attendance as required
Session student view
Tapping on Students inside the session card shows the full list of students linked to that session
This allows quick reference without entering attendance mode
What Controls Student Visibility
Student visibility inside sessions depends on:
Batch enrollment status (Active, Paused, Ended)
Session timing (past vs upcoming)
Batch-level roster updates applied before the session
Past sessions retain the original student list for record integrity.
Why This Design Matters
Building session rosters from the batch ensures:
No manual duplication of student lists
Accurate attendance tracking
Clean inputs for reports and AI insights
Consistency across sessions in the same batch
It also prevents accidental inclusion or exclusion of students.
Summary
Students appear inside sessions automatically based on the batch roster. When you open a session, active students are available for attendance marking and can be viewed directly from the session card. This design keeps session delivery efficient, accurate, and tightly connected to batch management.