Skip to content

Notification Settings

PodcasterPlus can tell you about a lot: chat messages, booking requests, episode invitations, finished AI jobs. Notification settings let you decide which of it reaches you, and how.

To get there, click Notifications in the sidebar, then Notification settings.

The Three Channels

Every notification type can reach you through up to three channels:

  • In-app: your Notifications inbox inside PodcasterPlus. This channel is always on
  • Email: switchable per notification type
  • Push: browser notifications on devices you've enabled, switchable per type. Some email-only types show Not available for push

Choose What You Hear About

Notification types are grouped into six cards, each with per-type Email and Push switches:

  • Episodes: invitation updates, like Episode invitations and Guest accepted an invitation
  • Collaboration: chat activity and notes, like Messages and mentions and Show notes updates
  • Team and bookings: Team invitations and responses and New booking requests
  • AI tools: AI transcription finished and AI guest research finished (email only)
  • Analytics: Download milestones when an episode passes 1k, 10k, 100k, or 1M downloads (email only)
  • Distribution: Distribution updates when your show goes live on a directory (email only)

Flip the switches you want, then click Save preferences at the bottom of the page.

There is no switch for support replies. When our team answers a request, the reply itself arrives as an email from us, and the app adds a notification so you can pick the conversation up in the Help and support panel. Turning that into a second email would just send you the same message twice.

Telling your team an episode went live

There is no switch for "an episode was published", because that one is better as an automation: you decide who hears about it, what it says, and when.

Go to Automations, create a rule, and pick the Episode Published trigger. Add a Send email step and set its recipients to All team members (or Producers or Co-hosts if you want a narrower group). Write the email once and every future publish sends it.

The same works for Episode Draft Created, so your producers can hear about a new episode the moment it exists rather than when it goes out. That one fires when someone creates an episode by hand from New Episode. Episodes that appear from a confirmed booking or an RSS import do not fire it, because they arrive through their own flows: use Booking Confirmed for the first of those.

Enable Browser Push

The Browser push card controls push for the device you're on:

  1. Toggle Allow browser notifications on this device
  2. Your browser asks for permission; allow it

If your browser doesn't support Web Push, the card says so. If you've previously blocked notifications for the site, re-enable them in your browser settings first.

Push delivery still respects the per-type toggles and your quiet hours.

Set Your Email Cadence

The Email cadence card decides how email notifications are timed:

  • Immediate emails: send email as soon as a rule says it should go
  • Daily digest: bundle eligible email notifications into a daily summary
  • Weekly digest: bundle them into a weekly summary

This only affects email. In-app notifications stay immediate, and push stays real-time.

Set Quiet Hours

Quiet hours delay email and push during the hours you choose; in-app notifications still collect in your inbox.

  1. Toggle Enable quiet hours
  2. Set a Start time and End time

Quiet hours use your current timezone, shown on the card.

Your Notifications Inbox

The bell in the header and the Notifications item in the sidebar both carry your unread count, and both lead to the same inbox.

The bell gives you the most recent activity without leaving the page. It opens on Unread, with All next to it, and a Priority tab appears whenever something urgent is still unread. On a phone it opens as a sheet from the bottom of the screen instead of a dropdown.

The Notifications page is the full inbox. Down the left is a list of inboxes:

  • All inbox and Unread
  • One per category: Episodes, Collaboration, Team, Bookings, and System (AI transcripts, media processing, and automation results)
  • Archived, kept separately from the rest

Each one shows how many notifications it holds, counted across your whole inbox rather than just the part currently on screen. On smaller screens the list becomes a picker at the top of the page.

Notifications are grouped under Today, Yesterday, and then by month, newest first. Unread rows are marked with a purple dot and a bolder title, and anything urgent carries an amber warning triangle. Each row says which category it came from and where it will take you, and clicking anywhere on the row goes there.

Acting on a Notification

Every row has two actions, on the row itself on a desktop and behind the ... button on a phone:

  • Mark read, or Mark unread on something you have already read and want to come back to
  • Archive, which moves it out of your inbox

Mark all read sits at the top of the page, and Archive read in the list header clears out everything you have already dealt with in the inbox you are looking at. When you are in a category inbox, Mark inbox read marks just that category.

Restoring Something You Archived

Archiving is not permanent. Open the Archived inbox and use Restore on any row to put it back, or Restore all to bring the whole archive back at once. A restored notification returns as read, so restoring does not change your unread count.

How Your Inbox Groups Things

Chat messages and show notes updates arrive in bursts, and a burst about one episode all leads to the same place. So your inbox collapses those into a single row labelled with how many there are, for example 7 related collaboration updates.

Opening that row takes you to the episode and clears every message in it at once, so your unread count drops by the full number. Mark read and Archive on the row do the same thing: they act on the whole group, including any updates further down your inbox than the page you can see.

A group only ever leads to one place. Anything with its own destination or its own decision to make stays as its own row:

  • Booking requests always appear individually, one per request, so every guest and every episode is reachable
  • Episode invitations, guest acceptances, and team invitations appear individually
  • AI, media, and distribution updates appear individually
  • Support replies appear individually, one per reply, and open that request in the help panel

The number on the bell counts individual notifications, not groups. A group of seven counts as seven until you open it.

Mute a Specific Podcast

Per-podcast delivery overrides let you mute activity from specific podcasts without changing the rest of your preferences. Toggle the switch next to any podcast to mute it; a Muted label confirms.

Pause Everything

The Pause all deliveries switch at the top temporarily suppresses notification delivery across inbox, email, and push. Flip it back off when you're ready to hear from PodcasterPlus again.

Monthly Notification Allowance

Browser push deliveries count toward a monthly allowance set by your plan, which resets on the 1st of each month. In-app notifications are always delivered, and notification emails count toward your plan's email allowance instead.

If the allowance runs out, further push deliveries are skipped for the month. Your Notifications page shows a banner telling you how many notifications were not delivered because your plan's monthly notification allowance was reached, with an Upgrade your plan link.

See Billing and Plans for how allowances work.

What's Next?

Was this page helpful?