Podcast Access and Report Emails Documentation

Each podcast in a workspace has its own list of people. That single list does two jobs: it decides who can see the show and it decides who gets emailed when a report for it finishes.

You manage it from Settings → Podcasts, then click the podcast's name (or Manage) to open its settings page. You need to be an Owner, an Admin, or a Manager of that particular show.

The podcast settings page

The page has three parts:

Settings — the show's name, feed URL, whether Audio Audit checks the feed automatically for new episodes, and the colour used to distinguish it on graphs. Turning Automatic checking off stops new episodes being analysed, and therefore stops the report emails that come with them.
Report notifications — the list of workspace members on this show, described below.
Workspace — a Remove from workspace button, shown to Owners and Admins only.

Viewers see the settings fields but cannot edit them.

Adding someone to a podcast

Under Report notifications, use the Add a team member search box. It searches the people already in your workspace.

Pick a name from the list to add them. They are added as a Viewer, so you never grant more than you intended.
Use the role dropdown on their chip to promote them to Manager — someone who can see the show, run reports for it, and edit its settings and notification list.
Click Extra… on a chip to tick individual extras on top of Viewer, without going all the way to Manager: "Edit this podcast's settings" and "Edit this podcast's notification list". Greyed-out lines are already covered by their role.
Click the × on a chip to remove them from the show.

If the person you want is not in the workspace yet, use Invite someone new… at the bottom of the search results — it opens the invite form with this podcast already selected.

Running reports and enhancing audio are not on the extras list. They spend the workspace's shared credits, so they are granted per person for the whole workspace on the member's own page — the panel links straight there. See Roles and Permissions.

Owners and Admins can already see and manage every show whether or not they are on this list. When one of them is on it, their chip shows their workspace role alongside their podcast role so a "Viewer" label is not mistaken for a restriction. For them, being on the list is purely about receiving the emails.

Who actually gets the report emails

Everyone on the list receives the show's report emails — both Managers and Viewers, because emails are not role-dependent. Four things all have to be true before an email is sent to someone:

They are on this podcast's list. There is no implicit audience: an empty list means nobody in the workspace is emailed about this show.
Their own row's email toggle is on. Each person can mute a single show for themselves.
Their global preference for that kind of report is on, in Settings → Profile under Email notifications — "Reports created from feeds" for automatic new-episode reports, "Reports created by team mates" for reports someone else started.
Their email address is verified. People who have not yet accepted their invitation do not get emails.

Whoever manually starts a report is always a candidate for its email, through their own "Reports created by me" preference, whether or not they are on the list.

Report emails are scoped to the workspace the report belongs to. If two workspaces watch the same feed, each holds its own copy of the podcast, gets its own reports, and notifies only its own list — no one sees the other team's activity.

Warnings and badges on the list

The panel tells you when the list will not do what you expect:

"Nobody is on this list yet" — the show is producing reports that email nobody in the workspace. This is the state a newly added podcast starts in.
"Nobody on this list will receive this podcast's report emails" — there are people on the list, but every one of them has muted it, turned their feed emails off, or has not verified their email address.
Pending on a chip — their email address is not verified yet; they will start receiving reports once it is.
Feed emails off — they have turned off feed report emails for themselves in their profile settings.
Muted — they have muted this particular podcast's report emails.

The reasons behind those badges are only shown to people who can manage the show.

Muting a show for yourself

If you are on a podcast's list, your own chip has an Email me reports toggle. Turning it off stops that show's report emails for you and nobody else — it does not remove you from the show or change what you can see. Viewers can use it too, even though they cannot change anything else on the page.

To stop report emails across the board rather than show by show, use the Email notifications section of Settings → Profile.

How people end up on a list

Nobody is ever added automatically. Rows come from two places, and both are visible at the time:

The invite form — ticking podcasts for a new member, with Send report emails left on, puts them on those shows' lists with emails enabled.
The notification list itself — adding someone from the search box, as described above.

That means a podcast you have just added to the workspace has an empty list until you put someone on it. Add yourself if you want its reports.

Removing a podcast from the workspace

Owners and Admins get a Remove from workspace button at the bottom of the podcast's settings page. Removing a show:

Takes it out of this workspace for everyone
Deletes its notification list, its colour, any name you gave it in place of the feed's own, and its automatic-checking setting, along with everyone's access to it
Keeps the reports that have already been created — they stay reachable, just no longer grouped under the podcast
Starts over if you add it again. Re-adding the same feed URL creates a fresh podcast entry with an empty chart, not the one you removed — its previous reports are not restored to it, you will need to rebuild the notification list from scratch, and it comes back under the name the feed itself publishes, so a show you had renamed needs renaming again
Its address changes too. The podcast you add back has a new id, so a bookmarked podcast page stops working, and so does anything of yours holding the old one — an API integration, a saved link in a document. Take the new id from the address bar on its settings page once you have added it back

It does not affect other workspaces, or anyone's personal workspace, that also follow the same feed — each holds its own copy of the podcast, untouched by what you do with yours.