Seeing Who Finished a Lecture
You turned a policy document into a narrated lecture and shared it with the team. The obvious next question is whether anyone actually watched it.
On a paid Scholarly Teams plan, a video lecture or podcast shared with your team reports who opened it, how far they got, whether they finished, and how they did on its questions.
This is reporting on material you shared with your own team. It is not monitoring: personal work stays private, and nothing outside the team library appears here.
Where to Find It
Two routes to the same table:
- From the item: open the lecture or podcast, press Share, then See who finished.
- From Team activity: open the Shared lectures section, which lists every lecture and podcast shared with the team and who has worked through each.
An empty list means nothing has been shared with the team yet. Share a lecture or podcast with the team and it appears here.
What the Table Shows
At the top, three figures for the item as a whole:
- Opened: how many of the team have opened it, as a count of total members.
- Finished: how many reached the end.
- Average score: the team's average on the item's questions, if it has any.
Then one row per teammate:
| Column | What it means |
|---|---|
| Person | The teammate's name |
| Opened | When they first opened it |
| Watched | How far through they got, as a percentage |
| Finished | Finished if they reached the end, Not yet if not |
| Questions | Their result on the item's questions, marked per question |
Each question is marked correct, incorrect, or not answered, so you can see which question a group of people got wrong, usually more useful than the score itself.
How the Numbers Are Counted
- Finished means they reached the end, not that they pressed a button to say so.
- Question results are their best attempt, not their first. The number of attempts is shown alongside.
- Only current members of the team appear. Someone who has left the team drops out of the table.
- Items shared with the team show Shared by so you know whose lecture it is.
Downloading the Table
Owners and Admins can press Download CSV for the full table: name, email, when they opened it, percentage watched, whether and when they finished, best score, and attempts.
Use it for a training record, or to join against whatever your team already tracks completion in.
Sending a Lecture Outside the Team
For people who are not in your workspace, a lecture made from a work document can be emailed to up to 10 colleagues at once. Each gets their own link, no account is needed, and you see how many opened and finished it.
This is the route for contractors, a client, or a department that is not on your plan. For teammates, share it with the team instead and use the table above.
What You Need
| Plan | A paid Scholarly Teams plan. On an unpaid workspace the option explains that seeing who finished and their quiz scores needs a team plan. |
| Who can see it | Any member can see progress on items shared with the team. Only Owners and Admins can download the CSV. |
| What's covered | Video lectures and podcasts shared with the team. |
| What's not | Anything in a personal library, private chats, and items shared only by link. |
See Scholarly Teams for what a paid team plan includes, and Managing Your Team for roles.
Good to Know
- Nothing is retroactive. Progress is counted from when the item was shared with the team.
- Re-sharing does not reset the table. The history stays with the item.
- A teammate sees their own progress, in the ordinary way any viewer does, their place, their score.
- Personal work is never included, even if you made it on a team seat. Only items in the team library appear. See Data, Privacy, and Model Controls in Teams.
Related
- Sharing with Your Team: how sharing into the team library works.
- Your Team Library and Team Projects: the shared library and team-owned projects.
- Managing Your Team: seats, roles, and billing.
- Turning Work Documents into Training: the path from a policy PDF to finished training.
- Interactive Video Questions: the checkpoints these scores come from.
- Data, Privacy, and Model Controls in Teams: what admins can and cannot see.