Why distribution matters as much as the content
Publishing a private audio inside a company solves one problem. Giving the intended audience a realistic way to receive it is a separate distribution problem. Supporting familiar podcast apps removes one possible access barrier.
When a listener can add internal audio to a compatible app, the update can sit alongside their existing listening. They do not need a Brandscast web player to receive new episodes.
RSS distribution in Brandscast adds a unique key per invited member and lets administrators revoke future feed access. The feed URL must be protected like a credential.
How private RSS distribution works in Brandscast
When you add a member to your Brandscast audio, the platform generates a unique RSS feed URL for that person. The URL includes a bearer key associated with their member record. Anyone who obtains that URL may be able to use it until you revoke or regenerate the credential.
What makes these feeds different from public RSS
A standard public audio RSS feed can be shared with anyone. Anyone with the link can subscribe and listen. Private RSS feeds in Brandscast are personal, authenticated and revocable. The URL contains the member's RSS key and must be treated as a credential; revoke or regenerate access if it is exposed.
A guided setup in compatible apps
Each invited member adds a personal feed to Apple Podcasts, Pocket Casts, Overcast, AntennaPod or Podcast Addict through the subscription page. Spotify does not support this private RSS workflow. Apps refresh feeds on their own schedule.
Security and access controls around each feed
RSS distribution in Brandscast is designed with security from the start. Each member receives a separate credential instead of one company-wide feed URL, and administrators retain member-level access control.
Revoke future feed requests
When an employee leaves or changes roles, you remove them from Brandscast and future requests through their personal RSS feed are rejected. Episodes already downloaded to their device may remain and need to be covered by your device and offboarding policies.
No public directory listing
Brandscast does not submit private feeds to public podcast directories. The RSS endpoint requires its bearer key, but the URL can still be forwarded or exposed and must be treated as a credential.
A familiar workflow for some listening habits
Internal communication tools have different access requirements. Private RSS can use a familiar listening workflow for employees who already use a compatible app, while others may need setup support.
Audio can fit selected existing routines
People may listen while commuting, exercising or doing approved light work. A compatible private feed can use those same safe moments. Whether this improves adoption is a pilot outcome, not a distribution guarantee.
Apps can refresh new episodes automatically
Once a member has added a personal feed, compatible apps can refresh new episodes without a Brandscast web login. Refresh timing and notification behaviour depend on the app and device.
How to set up RSS distribution with Brandscast
Create your private audio
Set up your internal audio in Brandscast, upload your first episode and configure your access settings.
Add your employees
Invite listeners by email. Each member gets a unique RSS key and subscription link generated automatically.
Members add their feed to a compatible app
Each member copies their personal RSS link and adds it to Apple Podcasts, Pocket Casts, Overcast, AntennaPod or Podcast Addict through the guided subscription page.
Publish and let the app refresh the feed
Compatible apps can fetch newly published episodes after a member subscribes. Refresh timing, downloads and notifications depend on the app, device and user settings.
Frequently asked questions about private RSS distribution
Can employees share their RSS feed with someone outside the company
The feed URL contains a personal RSS key and must be treated as a credential. If it is exposed or shared, an administrator should revoke or regenerate that member's access. As with other downloadable files, copies already saved to a device may remain there.
What happens to the feed when I remove a member
Future requests through their personal feed are rejected, so it no longer returns protected audio or new episodes. Files already downloaded to a device may remain there and need to be covered by your device and offboarding policies.
Which podcast apps are compatible
Brandscast supports apps that accept a custom authenticated RSS feed, including PulsarCast, Apple Podcasts, Pocket Casts, Overcast, AntennaPod and Podcast Addict. Spotify does not support this private RSS workflow.
Do employees need a Brandscast account to listen via RSS
Each invited member needs an access record in Brandscast. That record generates the personal RSS key used by the feed and lets administrators revoke future access without requiring the member to use the web dashboard.
Start distributing your internal audio via private RSS
Give each invited listener a revocable feed credential for a compatible podcast app, without publishing the audio in a public directory.
Start trialPilot the subscription flow with a small group before a broader rollout.