One group per site, episodes for each

The Lyon plant hears Lyon's news; everyone hears the management update

User groups sort your employees by site: Lyon, Nantes, headquarters. Each group has its own podcast sections, closed to the others, while a shared section opens to every account. Someone moves to another site? Change their group in the back office and their episodes follow. Nothing stops an account from sitting in two groups, a site and a trade for instance.

A podcast only your employees can hear

Signing in is mandatory, and you are the one who opens accounts

Authentication puts a login between every user and the episodes. Create the accounts yourself from the back office, or let employees sign up and only place them in a group once checked: as long as an account belongs to no group, the internal sections stay closed to it.

The industrial group with four plants

A safety episode per plant every Monday, the quarterly management update for all; night shifts listen to it on their break.

The network of bank branches

Regulatory updates in ten minutes every Friday, by region; advisers download them for the morning commute.

The firm that wants to sell its finance podcast

When the episode is meant for the public and has to be paid for, it takes the other setup: a subscription sold on the stores.
The subscription learning podcast

Three companies, three internal podcasts

Yours? Record a first episode, set up two groups and try it: one month on us, no credit card.

Audio goes where email never arrives

On the loading dock, on the road, in the workshop: an episode needs no screen

Drivers, technicians, store staff: many of your people never sit in front of the intranet. Five minutes of audio fit into a drive, phone in pocket, thanks to background playback in the native apps. Downloaded the night before from favorites, the episode also plays deep in a warehouse or on a site with no signal.

Launching the internal podcast: five settings

All from the back office, before the first episode.
  1. Accounts

    Turn on Authentication; create the accounts or approve sign-ups.
  2. Groups

    One group per site, plus any others you need: managers, newcomers.
  3. Sections

    A Podcasts section per site, reserved for its group, and a shared section.
  4. Notifications

    A manual push addressed only to the group concerned, sent right away or scheduled.
  5. Onboarding

    A few intro screens at first launch, with App Walkthrough.

Teams talk back

A question for management, an idea for the next episode

A Form section collects employees' questions, which the communications team gathers into the monthly Q&A episode. The built-in dashboard shows which content gets the most views: you see which topics land, and adjust the editorial line.

AI working for the communications team

Three examples, in the back office and from your assistant.
To publish

Monday's episode prepared from ChatGPT

The MCP server links the app to the assistant your team already uses: hand it the script, it prepares the episode page and the push meant for the Nantes group; you review, you confirm, it runs.
Included
To translate

The episode page for the Barcelona site

One-click translation in the back office moves a page's text into another language while keeping its tone. The audio itself still has to be recorded in the site's language.
To welcome

The newcomer's path

Describe in the back office a list of the ten episodes to hear in the first week, ticked off one by one: the AI Extension Builder builds that checklist as an app section. One example among many of what a description can produce.
Free

Also in the internal podcast app

Episode pages

An article next to the audio: the figures quoted, the links, the documents.

Content that expires

An end-of-publication date removes an outdated announcement by itself.

An internal agenda

Seminars, site visits, team meetings, in an Agenda section.

Several editors

Team accounts with their own rights: publish, send a push, update the app.

Favorites

Everyone keeps aside the episodes they want to hear again.

A web app

Employees without a work phone sign in from a browser.

Business podcast: frequently asked questions

What are the benefits of a podcast for a business?

It reaches employees who are not in front of a screen, it gives a voice to management and teams alike, and it can be heard while doing something else. In an app under your name, it stays internal: only the accounts you approved can hear it.

How do I keep the podcast for employees only?

With Authentication and User groups: internal sections only open to accounts placed in a group, and you are the one who places them. You can also create every account yourself.

Can an episode concern a single site?

Yes: publish it in the section reserved for that site's group, and address the push to that group only. Other sites don't see it.

Do employees have anything to pay?

No. This app runs on Authentication and User groups, which cannot be combined with Memberships. Nothing is for sale in it.

What about selling a business or finance podcast to the public?

That is the opposite setup: a subscription bought in the app, with episodes reserved for subscribers. It is built in a separate app; the educational podcast app shows how.

What budget for an internal podcast app?

Premium with two options, Authentication and User groups, or Pro, which builds them in. Hosting, push and updates are covered; the storage space for episodes depends on the plan.

What an internal podcast app costs

The iOS and Android apps start with Premium. Keeping access to employees relies on two options, Authentication and User groups, which Pro includes from the start. Since nothing is sold in the app, Memberships does not enter the calculation.
Premium · iOS, Android and browser55€ /month, billed yearly
Authentication, an option on Premium12€ /month
User groups, an option on Premium5€ /month
Pro · both options included105€ /month, billed yearly
Apple and Google developer accounts are paid separately, to them. The bandwidth used by plays is not billed to you.

Pioneers of no-code

15 years of experience building native apps for businesses and content publishers. And the numbers to prove it.
25 000+
Daily downloads for apps built with GoodBarber*
30 000+
Clients have brought their app projects to life with GoodBarber
2011
The year GoodBarber was born: no-code, before anyone else

* Source: internal download tracking, App Store and Google Play, April 2026.