Your workspace's first podcast

The first podcast a workspace creates sets the tone for everyone's expectations, so Quorum times the prompt deliberately. An episode generated before anyone has set up a profile is personalised to no one, and a generic first episode undersells what the product does.

When the prompt appears

After admin setup finishes, the dashboard waits until the team is ready. The readiness check is simple: at least 75 percent of the workspace's active members have saved their podcast profile, and no podcast exists yet. Once both are true, admins see a prompt on the dashboard inviting them to create the first podcast.

Quorum keeps this check fresh in two ways. It re-evaluates every time someone saves their profile, and it also sweeps periodically in the background, so members added or removed in the accounts system are reflected without anyone touching the podcast app.

Getting the team ready

Every member sets up their own profile once, guided by a welcome flow on their first visit to the dashboard. A profile takes a couple of minutes: domain, role, interests, and any custom instructions. The more of the team completes it, the more genuinely personalised the first episodes will be. Encouraging the team to finish their profiles is the one thing an admin can do to move the milestone forward.

Creating the first podcast

The prompt leads to the Create your first podcast page. The guidance there is worth following:

• Pick a real upcoming meeting rather than a test. Real documents and real attendees show the product at its best.
• Enter meeting goals. They steer which files are picked and what each episode emphasises.
• Every attendee who has set up their profile gets their own personalised briefing.

The page uses the standard three-step meeting wizard, so nothing here is different from the meetings you will create every week afterwards.

After the first podcast

Creating the first meeting permanently retires the prompt for the workspace. It never reappears, even if meetings are later deleted, so the dashboard stays focused on current work rather than re-running onboarding.