Release 4.2 closed in Jira. Find what needs training and brief Sales, CS, and Support by Wednesday.

Release 4.2 · Support
The new flow, a day before launch
25%complete
Your LLM reads what shipped. Juno briefs each team, once you approve.
Release 4.2
Sep 10 to Sep 16By Friday, you have rebuilt one course, rewritten four team briefs, and answered the same question ten times. Two sprints later, the feature is still explained wrong.
Release 4.2 closed in Jira. Find what needs training and brief Sales, CS, and Support by Wednesday.

Release 4.2 · Support
The new flow, a day before launch
25%complete
ThuSep 10
FriSep 11
Triaged
MonSep 14
Four briefs, one per team
TueSep 15
Maeve M. · 9:40
WedSep 16
Ready before release day
ThuSep 17· Ships
What's new · Beta
Notification settings
Choose Email, Slack, or in-app for each notification type, and know where learners still see reminders.
3 min4 steps1 checkPass 80%
Passed · 100%
Lesson complete
Email is off for training reminders. Learners still get them in Slack and the in-app bell.
CompletionScoreTimereported to Juno
juno
Welcome back, Hyejin
Here's what's happening in your workspace.
NewNotification settings are here, under Admin.
juno
Admin
People, content and workspace settings
juno
Admin
People, content and workspace settings
Notifications
Choose how people hear about each notification type. The in-app bell always stays on.
juno
Saved · email off for training reminders
Admin
People, content and workspace settings
Notifications
Choose how people hear about each notification type. The in-app bell always stays on.
Email is off for training reminders. Where will learners still see them?
You picked A · Nowhere
Not quite. The in-app bell never turns off. Slack is still on for training reminders too.
You picked C · Only in email
Not quite. The in-app bell never turns off. And email is the one channel you just switched off.
Every score is reported back to Juno.
Section 2 · Inviting people
Only workspace owners can invite new members.
Owners and admins can invite new members.
Release 4.2 · Permissions, line 3


JadenUpdate the course for Release 4.2, Permissions
Only what changed is rewritten; the rest stays word for word. Every save keeps the previous version.
Sections changed
Only the sections affected by the release are rewritten. Everything else stays word for word.
Each proposed edit links to the part of the release note it came from.
Each time you publish, the previous version is kept, so nothing your teams learned is lost.
The course your reps open on Thursday already covers what shipped.
Only the sections affected by the release are rewritten. Everything else stays word for word.
Each proposed edit links to the part of the release note it came from.
Each time you publish, the previous version is kept, so nothing your teams learned is lost.
The course your reps open on Thursday already covers what shipped.
Release 4.2
12 changes
Every change is sorted into one of three priorities: Mission-critical; Important, not urgent; or Nice to know.
Your LLM reads the release and proposes a priority for each change.
Juno's tools are built and documented so your LLM can run them and chain them together.
You approve the triage before any course, post, or assignment goes out.
Juno acts within your existing Juno permissions.
When the release comes from a vendor, not from you: Tool & Vendor Enablement
See securitySee Juno in your LLM
Role, department, location, or group decides who gets which brief.
Each assignment carries a due date the day before the release date.
Each team's brief goes out in the languages that team works in.
Each team's Juno channel posts the brief to its linked Slack channel.
Role, department, location, or group decides who gets which brief.
Each assignment carries a due date the day before the release date.
Each team's brief goes out in the languages that team works in.
Each team's Juno channel posts the brief to its linked Slack channel.
“Don't tell me who completed training. Tell me what changed.”
the biggest drop comes after the call, not the course
correlation, never causation
Readiness is measured for each team on every release, before launch day.
Each team lead confirms their team is ready before release day.
Each team takes a post-release quiz with its own passing score and deadline.
The Behavioral Change Signal tracks the feature from the course to how people use it.
Your releases become short lessons and videos, filed by product area.
Your AI asks you
Where your release notes live, who it's for, your product areas, how far back
I want a Product Hub channel in Juno Journey: one place where people learn what we ship, easy to refresh from our release notes whenever I ask. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. Where our release notes live (a tool, a docs site, or I paste them) 2. Who the channel is for (customers, our own staff, both) 3. Our product areas, to use as topics 4. How far back to go Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or paste/upload the notes. Never invent a release. Search Juno first for lessons on these features and any existing product channel, and reuse what fits. Then propose the channel: a topic per product area, existing content filed in, and a draft lesson for each gap. Build it as a new private channel and preview it. Adding content to a channel with members notifies them, so ask before touching an existing one. Don’t publish or notify anyone until I approve.
Your new screens, rebuilt from screenshots and tracked as SCORM.
Your AI asks you
Where the release note lives, screenshots of the new screens, who it's for, the pass mark
I want to turn a product release into a click-through lesson in Juno Journey: people practice the new flow, answer a quick check, and the score reports back to Juno. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. Where the release note lives (or I’ll paste it) 2. Screenshots of the new screens (I’ll attach them) 3. Who the lesson is for 4. The pass mark Ask these in one message, then wait for my answers. If the release note lives in another tool, check it’s connected in this chat; if not, I’ll paste it. Rebuild each screen in HTML to match my screenshots; never invent UI. Search Juno first for training on this feature, and update it if it exists. Then outline 4-6 steps that mirror the real clicks, with hotspots and short coaching, plus a knowledge check. After I approve, build it as an interactive HTML lesson with SCORM tracking and preview it. Saving it to Juno puts it live in our catalog, so save only when I say so; don’t assign it.
This month's releases in one short course, plus a video on the biggest one.
Your AI asks you
The date range, where your updates live, who it's for, your brand colors
I want this month’s “What’s new” digest in Juno Journey: one short course on what we shipped, plus a 60-second explainer video for the biggest change. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. The date range 2. Where our updates live (release notes, a changelog, or I paste them) 3. Who it’s for (customers, sellers, support, everyone) 4. Our brand colors Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or paste the updates. Never include a change I can’t trace to the source. Look in Juno first for courses that already cover these features, and update them instead of repeating. Then list the changes by product area and propose which one gets the video. Build the digest as a draft course with a short quiz. For the video, show me the storyboard and render only after I approve it, then add it to the draft course. Don’t publish, assign or notify anyone until I say so.
A quick check on a launch's key facts, with a due date and a drafted nudge.
Your AI asks you
The topic or course, who takes it, the deadline, the pass mark and attempts
I want a quick 5-question drill in Juno Journey that locks in the key facts after a launch, with a due date so it actually gets done. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. The topic, or the course it should reinforce 2. Who should take it 3. The deadline 4. The pass mark and how many attempts Ask these in one message, then wait for my answers. Find that course or lesson in Juno first and base every question on it. If the material lives outside Juno, check it’s connected here; if not, I’ll paste it. No questions you can’t trace to the source. Show me the 5 questions with answers and one-line explanations. After I approve, build the quiz as a draft and prepare the assignment with the deadline as its due date. Tell me plainly what Juno reminds people about on its own; you can’t schedule repeats or reminders from this chat. Draft a nudge I can send later. Show me who would get the assignment and the nudge, but don’t assign or send anything until I explicitly say go.
“The journeys with automations really helped me make sure my support agents were being kept up to date on our product on a daily basis.”