Three wishes that pull in different directions
Anyone who sells an audio course, a members-only series or a training program to a closed group runs into the same three wishes:
Easy access. One click, no account, ideally in the podcast app people already use.
Protection. Only the people who paid can listen, and access stops when the license ends.
Reporting. The buyer wants to know whether their people listen, and sometimes how far each person got.
Each wish is reasonable on its own. The trouble starts when you ask for all three at their strongest.
The routes below differ on two separate points: what they ask of the listener, and what they let you see or switch off. A personal link asks for nothing at the moment of listening, yet it belongs to a known member you can remove. A sign-in alone adds no progress data. Progress per learner comes from Springcast LMS, an add-on for organizations that train their own staff.
Where this question came from
We recently discussed this with a prospect who wanted to offer an audio series to organizations for their staff. Their first idea was one shared access code per buying organization, used by all of its staff, with no email addresses involved.
In the same conversation, they also wanted totals per buying organization, and access that stops when a license ends.
The wishes are fair, and they pull against each other. A code shared by a whole organization can't be switched off for one person. Whether you still see totals per organization depends on how codes are issued and counted. Ending access per person means knowing who each person is: an email address for a member link, an account for the app.
A worked example: one course, three routes
The example below is illustrative. Suppose an agency produces a twelve-episode audio course for a client. The client sells access to participants in six-month cohorts. It also wants its own staff to take the course as part of their training.
For every route, the agency asks the same five questions. How are people invited and how do they open it? What happens if they forward it? How does access end, and what can the client report?
Route 1: members-only podcast with personal links
With the private option Members only, a podcast is open only to the people on its member list. The public website and public RSS feed are switched off.
Invite: add participants by email, one at a time or by CSV import. Each one receives a welcome email with a personal link.
Open: participants listen on the podcast website through that link. No account, no password.
Forward: a personal link can be forwarded. Resetting it makes the old link invalid. Episodes someone already downloaded stay on their device.
End: remove a member or give them an expiry date, and their access to the website, player and personal feed ends.
Report: show and episode analytics for the whole group. There is no progress record per member.
Members only is included on Professional (up to 250 members per show) and Scale (unlimited). The player can't be embedded on another site for a members-only show.
Route 2: personal RSS feeds in the listener's own app
On Scale, each member can also get a personal RSS feed, switched on or off per show. Participants add it to a podcast app that supports custom RSS links, and new episodes appear there.
Invite and end: the same member list as route 1. Removing a member also ends their feed.
Open: in an app they already use. Check beforehand which apps your participants use and whether those apps accept private feeds.
Forward: a feed address can be shared like a link. A reset makes the old one invalid.
Report: the same show and episode analytics as route 1. Downloads count episode requests, including from other podcast apps, but a download doesn't prove anyone listened. Completion and listened percentage come only from the Springcast player, so they don't cover those apps.
Manage at scale: Scale includes an API for member management, so your own sales or contract system can keep the list current.
Professional does not include personal RSS feeds or the member management API.
Route 3: Springcast LMS for the client's own staff
Springcast LMS is an add-on for onboarding and employee training. Learners use Springcast Mobile, an invitation-only app. The episodes become lessons in a course, and each employee is a learner. In the example, this route covers the client's own staff. For paying participants outside the client's organization, plan on routes 1 and 2.
Invite: by email invitation, CSV upload, a shareable invitation link or, for an organization that uses SSO, linked Mobile groups. Cohorts can have a start and end date.
Open: learners install the app and sign in. That is the extra step this route asks for.
Forward: access runs through each learner's own account.
End: you manage enrollment per learner and per cohort.
Report: progress per learner against the completion rule you set, quiz results and certificates when you switch them on.
You choose when a lesson counts as complete: when the learner starts it, or when playback reaches a percentage you set. That percentage is playback position, so skipping ahead counts. A quiz is the separate check for knowledge. Springcast LMS is available as an add-on on Company and in Enterprise. Learners use the mobile app; the browser portal is coming soon.
The three routes side by side:
What gating can and cannot do
Three limits apply to every route, and it helps to say them to a client early:
Copying. We don't promise copy protection on any route. Personal links can be forwarded and downloaded episodes stay on a device. What you can do is end access and reset links.
Learning. A completed lesson means the completion rule you set was met: the learner started it, or playback reached your percentage. That says nothing about listening time, attention or understanding. Use a quiz when the client needs a knowledge check.
Payment. Springcast doesn't sell access for you or run a paywall. Your own checkout or contract decides who joins; you then add those people as members or learners.
Choose the concession first
Start with the trade-off you can live with. The feature follows from there.
The lowest barrier matters most, and a forwarded link is acceptable: members-only with personal links.
Participants want their own podcast app, and you can manage feeds: add personal RSS feeds on Scale.
The client trains its own staff and needs progress per learner, or a course with steps and quizzes: Springcast LMS. Accept the app sign-in and set the completion rule on purpose. A quiz is what checks knowledge.
Serving several client organizations? A separate workspace per client keeps their content and statistics apart. Multiple workspaces and role-based access are part of Springcast, though not every plan includes them.
How Springcast fits paid audio
Springcast offers all three routes, so you can match the route to the client instead of the other way around. They sit on different plans. Member links are on Professional and Scale; personal feeds and the member API are on Scale. The LMS is an add-on on Company and in Enterprise.
When a client wants a structured course for its own staff, your episodes can become lessons. LMS lessons link to the audio and video items you manage under Content.
For the broader picture of who uses private podcasts and how to set one up, read our guide to private podcasts for business. For courses, see Springcast LMS.
Test your route with your own scenario
Tell us who your participants are, how they should get in and what your client needs to see. We'll walk through the route that fits, including what it can't do. Contact Springcast.