Why coaching video is different
A course lesson is made to be watched by every student. A coaching call recording is made for the people who were in the room, and it may include their questions, their numbers and their names. A leaked replay is a trust problem with your clients, not just lost revenue. The goal is simple: each cohort sees its own sessions, and anyone who shares one knows their name is on it.
One role per cohort
WordPress roles are the cleanest way to separate cohorts. Create a role per cohort or program tier with a role plugin, or let your membership plugin assign one, then set Restrict to Role on each recording. The match is exact, so the spring cohort cannot open the autumn cohort’s calls. Administrators always pass, so you and your team can check any recording. See who can watch.
If you run cohorts as courses in LearnDash, Tutor LMS or LifterLMS, Pro’s Require enrollment to watch does the same job from the course enrolment instead of a role. See LMS and course plugins.
The client’s name on the replay
At Standard protection the viewer watermark shows the client’s display name and IP while the recording plays, moving between the corners and the centre every 30 seconds by default. Lower the Position Swap Interval to 10 or 15 seconds to make it harder to crop out of a recording. Set Opacity around 0.3 to 0.5 so it is visible without getting in the way of a slide or whiteboard. See viewer watermark.
Pro lets you choose what the watermark shows from seven fields, such as email and a timestamp, which is useful when several clients share a first name.
Who caught up
After a live call, the useful question is who watched the replay and how far they got. MediaShield > Viewers lists each client with videos watched, average completion and last active time, and opens their history. Milestones fire at 25, 50, 75 and 100 percent watched for logged-in clients, and a developer can hook those to send a follow-up. See watch analytics.
Hosting the recordings
Upload recordings wherever you already keep them: unlisted YouTube, Vimeo, Wistia or Bunny Stream, or straight to your own server from Videos > Add New. For platform videos, also use the host’s own privacy settings, because an embed always carries its video ID. For self-hosted files, MediaShield plays them through a permission-checked address; on an nginx server, add the rule shown under Tools > Site Health so the files cannot be fetched directly. See keep your video host.
What it will not solve
MediaShield does not record or schedule calls, and it has no captions or chapters. It does not stop a client recording their screen; it makes the recording traceable.
Common questions
Can each client only see their own recordings?
Yes, if each client has a role of their own and each recording is restricted to that role. For one-to-one coaching at scale that is a lot of roles; most coaches restrict by cohort or program instead.
Can I let a prospect watch one sample session?
Yes. Set that one video’s Protection Level to None and it plays for anyone, with no login, watermark or tracking. Every other video keeps its own level.
Does it work on phones?
Yes. On players narrower than 640 pixels the watermark shows the name only, so it stays readable. The IP is still recorded with the session.