Use Cases
Run a Meetup and Confirm Attendance
Schedule a meetup in Create, then Submit attendance list in Follow Up.
Situation
You’re running a live session and need people to sign up for an occasion, then lock who attended so results (and certificates) can complete.
Outcome
The meetup is published with occasions; learners sign up in Learn; after the occasion ends, an administrator updates the Attendance list and clicks Submit attendance list in Follow Up. People marked as attended can finish in Learn, and certificates can issue when configured.
Who
Collaborators and administrators create the meetup in Create. Only administrators submit attendance in Follow Up. Learners sign up in Learn.
Path
- Create and configure the meetup (occasions, capacity, visibility) in Meetups.
- Set certificate issuance if needed — Certificate Configuration.
- Learners choose an occasion in Meetups in Learn.
- After the occasion has ended, open Meetup Attendance: mark who attended on the Attendance list, then Submit attendance list (and confirm you cannot change it afterward).
- Learners with a passing result find certificates in View and Download.
Tips
- Meetups cannot currently be marked Mandatory the way courses can—you still assign visibility.
- You can start marking checkboxes after the occasion starts, but Submit attendance list stays disabled until it has ended.
- After submit, the button shows Attendance list submitted—there is no edit path. If nobody was on the list, you may see Submit 'Nobody attended' instead.
- Collaborators and managers do not finalize meetup attendance in Follow Up—that step is administrator-only.
