One release starts both lanes: the academy, the certification, the partner briefing. Each ends on its own number.
CalendarNorthwind Academy
The academy stays level with the product.
Search your Northwind AcademySearch
Channels
What shipped in 4.2
Updated Sep 17
Scheduled exports, click-through
Updated Sep 17
Exporting reports
Updated Sep 10
Northwind certification
Updated Aug 30
Trusted by teams at
Every release starts three weeks of updates to the academy, the certifications and the partner briefing, done by hand or not done.
How it works
1Trigger & Signal
2Knowledge Design
Your LLM + Juno MCP
3Delivery & Adoption
4Measure
accounts trained before the renewal, firms still certifiedOne release, one journey
Every platform in this category hands you an academy and leaves the scheduling to you, so keeping the content true costs a small team its week. Here the change starts the work: your LLM reads what shipped in your own release notes, judges which accounts and partner firms it touches, and drives Juno from there. Nothing leaves the building until you say so.
Release 4.2 ships Thursday. Update the customer academy, brief its accounts and re-certify Gold partners.
Channel · for customersWhat shipped in 4.2Updated in placeWhat shipped in 4.2
by Northwind
Updated Sep 17
Scheduled exports, click-through
by Northwind
Updated Sep 17
Exporting reports
by Northwind
Updated Sep 17
Hundreds of apps are reachable this way. Your release notes, your issue tracker and your wiki are read by the assistant your company already pays for, which then drives Juno.
Scheduled exports, adoption by account
Release 4.2 · 212 accounts · 30 days after launch
Two lanes
A partner leader reading a customer-education page recognises nothing in it, and a customer-education leader reading a partner page recognises less. The two lanes share an engine and a triage. They share very little else, so this page says the difference out loud instead of averaging it into one promise.
If a person matches all of the criteria:Feature in use: Exports, assign What shipped in 4.2.
Customer provisioningIf a person matches all of the criteria:Partner tier: Gold, assign What shipped in 4.2.
9 Gold partner firmsAccount view
Her budget depends on one answer at the renewal review, and what this category exports is a list of learners who finished something. The unit here is the account. Juno writes learning activity onto the customer's contact and account record in Salesforce: what was assigned, what was completed, the quiz result and the expiry. Trained and untrained accounts become a comparison your CCO runs in her own tool.
Juno Learning Activities (4)
What sits beside that comparison as direction. Ticket volume for trained accounts, adoption of the shipped feature and renewal per cohort come from your own helpdesk, product analytics and CRM. They are yours to read, and we do not publish them as ours. Salesforce integration
Certification
A certification is a claim your partner firm makes to its own customer, which is why it carries a date and is refreshed when the product moves. Juno issues it after the checkpoints, at the end of a certifying journey or from attendance at a live session, tracks it, expires it and reminds before it lapses. The release that invalidates one puts the firms holding it back through it.
Credentials issued before Juno come with you. Existing certificates upload in bulk from a spreadsheet, so a programme that predates Juno does not restart at zero. Certify your partners
Workspaces
A customer academy and a partner programme sit in one branch because they run on one engine, and they need separate entrances because nothing else about them matches. Each audience gets a workspace of its own: its own branding, domain, administrators and sign-in. A module you maintain once is reused across them, so keeping two audiences current does not mean writing it all twice.
Putting other companies' people into your system is the IT question on this family. Customer contacts become learners from a filter you write on your CRM, with a dry run before anything is created, and a one-hour magic link instead of a password, or your organisation's SSO where that is in force. Tenant isolation and least privilege, ISO/IEC 27001 certified, GDPR and CCPA.
A branded public homepage with your real courses, previewed before it goes live.
Your AI asks you
Your website, who it's for, programs to feature first, what must stay private
I want to design the homepage of our customer academy in Juno Journey: the public page customers land on to learn our product. 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. Our website, so you can match our colors, fonts and logo 2. Who the academy is for (new customers, admins, end users) 3. Which programs or certifications to feature first 4. Anything that must stay private Ask these in one message, then wait for my answers. If you can’t open our site, I’ll paste colors and logo; don’t guess. Check our Juno first: today’s public academy pages, navigation, and which published courses are ready to feature. If you have no public academy tools here, say so; don’t edit our internal academy instead. Then draft the homepage: hero, a link into the course catalog, a “Start here” row, featured programs from our real courses, and navigation. A new public page goes live when saved, so preview it and save only when I say so. Don’t change the live site until I explicitly approve.
Tiers, exams and the gates between them, drafted as journeys you approve.
Your AI asks you
Tiers, what partners must prove, pass mark and attempts, your site, any docs outside Juno
I want to launch a partner certification academy in Juno Journey. 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. Our partner tiers and what each tier unlocks 2. What a partner must prove to be certified at each tier 3. The pass mark and how many attempts 4. Our website, so the pages match our brand 5. Whether we keep partner material outside Juno, and where Ask these in one message, then wait for my answers. For anything outside Juno, check it’s connected in this chat; if not, I’ll connect it or upload files. Never invent partner content. Look in Juno first for existing partner courses, quizzes and academy pages, and reuse them. Then propose one journey per tier, each ending in a certification quiz, plus a public academy page for partners that shows the tiers. Show me the outline, then build the courses, quizzes and journeys as drafts. A new public page goes live when saved, so preview it and save only when I say so. Don’t publish, assign or invite partners until I approve.
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.
Usage side by side for accounts whose owners took the training and those who didn't, labeled as correlation.
Your AI asks you
The feature, whether and where you track usage and account owners, the "used it" event
I want to compare feature adoption for accounts whose owners took the training vs. those whose owners didn’t. 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 feature, the training that covers it, the date range 2. Whether and where we track product usage, and which event means “used it” 3. Where account owners are recorded (if anywhere) and how they match Juno users 4. Accounts or segments to exclude Ask these in one message, then wait for my answers. Check each non-Juno source is connected in this chat; if not, I’ll connect it or upload a CSV. Never estimate missing numbers. Pull completions from Juno first and show how you matched people. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Then build an interactive artifact: adoption for trained vs. untrained owners, counts per group and the account list. State definitions, show sample sizes and gaps, and say plainly it’s correlation, not causation. Change nothing anywhere.
“Influenced 85%+ of direct customer ARR with Hunters Academy (our customer & partner certification program in Juno). It is becoming a company differentiator used to help close new business, supporting fast time to value for our customers.”
Customer Onboarding
Saved $60,600 (105 live customer success training hours) in 1-year with a technical customer onboarding certification in Juno.
Partner Onboarding
“Our certification program is key to enabling the partner & MSSP ecosystem, and onboarding at scale.”
Each moment has its own demo and its own signal. Start with the one that is costing you now.
Two doors into the product itself. The branded academy, in-product surfacing, credentials, monetization with Stripe, syndication and embed live on the audience pages.
