Juno finds everyone a new policy applies to, updates the training, collects each acknowledgment and shows who is done, so nothing slips before the audit.
4.7 / 5G2
Analytics
Last 30 days
Emails, reminders and a spreadsheet of who signed: every policy change turns into weeks of chasing.
How it works
1Trigger & Signal
2Knowledge Design
Your LLM + Juno MCP
3Delivery & Adoption
4Measure
Days from publication to current, on this versionLegal published data-retention v3. Roll it out to everyone it binds, with a check and an acknowledgment.
Data retention policy v3
What changed in v3, a 5-question check and an acknowledgment.
Steps: 0 of 3Due: Sep 30
Each learner's record names the published version of the course they saw.
The quiz result and its attempts sit on the same row as the version.
A signature, a certification or a pass: the record says which one.
Filter to one policy, save the view and export it as a CSV.
JunoRoll out Data retention v3 to everyone the clause applies to, due Sep 30
1,652 people match: 1,412 employees and 240 contractors.
I'll assign "Data retention policy v3" to 1,652 people.
These 1,652 people will be enrolled and see it in their feed.
Role, position, department, location, group and employee type decide who is bound.
Contractors are an employee type, so the rule scopes them in or out.
A dry run counts the people a rule will touch before anything sends.
The compliance owner signs the scope off before anyone is assigned.
For the people who join after this rollout: Company & Dpt-Wide Orientations
§ 4.2 Customer data in support tickets
Agents may keep customer attachments in a ticket for 24 months.
Agents delete customer attachments from a ticket 90 days after it closes.
JadenUpdate sections 2 and 4 of last year's course
PDFData retention policy v3Two sections change, and a 5-question check and an acknowledgment are added.
Sections changed
Your model reads what changed between the two versions of the document.
Mission-critical, Important, not urgent, Nice to know. The change lands in one.
Confluence, Notion, SharePoint, the GRC tool or the audit tracker, reached by your LLM.
Last year's course is updated as a draft, then published as the new version.
Juno acts within your existing Juno permissions, over OAuth, with no API keys.
The same loop runs on a product release: Release & Product Update
See securitySee Juno in your LLM
If a person has not startedtheir training after 7 days, send them a nudge.
If a person has not completedtheir training 7 daysbefore their due date, send them a notification.
If a person has not completedtheir training 1 daybefore their due date, send them a notification.
If a person has not completedtheir training 2 daysafter their due date, send them a notification.
Notifications go out 7 days before, 1 day before and 2 days after.
Two automation actions, on a rule you set, for whoever has not started.
Each manager sees who on their team is overdue.
A certification you created carries its expiry date and its reminders.
Reminders stop for each person once their work is complete.
Tue4 pm
Wed
1,412 people
Wed
Day 7
Day 14
Day 30
Day 30
These teams planned their compliance season before it started. The completion figures are theirs, in their own words.
“Running our compliance season with Juno was a huge success. With everything planned out in advance from automated assignments and reminders to real-time analytics, we were able to drive 100% completion across the org.”
“…smooth, structured, and highly effective… over 90% completion across the company, and the process felt completely under control from start to finish.”
Trained thousands on key topics including compliance, information security, financial monitoring and personal safety.
85–98% completion on mandatory programs
76% of employees rated Juno 9 or 10
The number to watch is not the share who acknowledged. It is the time between publication and a population current on this version.
Data retention policy v3
by Northstar
Course
Updated Sep 15, 2026
A short course, a 5-question check and an acknowledgment, with a clear list of who's done.
Your AI asks you
The policy document, who must complete it, the deadline, acknowledgment or quiz
I want to roll out a new policy in Juno Journey with proof that everyone who needs to has read and understood it. 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 policy document (upload it, or tell me where it lives) 2. Who must complete it (departments, locations, roles) 3. The deadline 4. Acknowledgment, a quiz, or both Ask these in one message, then wait for my answers. If the document lives in a tool outside Juno, check it’s connected in this chat; if not, I’ll upload it. Stick to what the policy says; don’t add rules. Search Juno for older versions of this policy training and update rather than duplicate. Then plan a short course (what changed, what it means for you, examples), a 5-question check with a pass mark, and an acknowledgment step. Show me that outline, the audience and the due date first, then build as drafts. Don’t publish, assign or notify anyone until I explicitly approve.
Teams down the side, topics across the top, so the gaps show up before the deadline does.
Your AI asks you
Which groups and topics, which courses count, what "done" means, the date range
I want a completion heatmap: groups down the side, topics across the top, and each cell showing how far along that group is. 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. Which groups (departments, roles, locations) 2. Which topics, and which courses count for each 3. What “done” means (completed, passed, above a score) 4. The date range Ask these in one message, then wait for my answers. Pull everything you can from Juno; if you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. If a grouping lives outside Juno (e.g. an HR system, if we use one), check it’s connected in this chat; if not, I’ll upload a CSV. Never guess anyone’s group. Confirm definitions with me, then build an interactive artifact: the heatmap with counts per cell, a click-through to the people in each cell, and the three weakest spots with suggested next steps. State definitions, show sample sizes, and grey out cells too small to judge. Don’t assign or notify anyone.
Claude checks your courses against your source of truth and lists what to fix first.
Your AI asks you
Where your source of truth lives, which topics matter most, what counts as a recent change
I want to find training in Juno Journey that no longer matches how things actually work today. 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 source of truth lives (product docs, release notes, policies) 2. Which topics or courses matter most 3. How recent a change must be to count 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 upload the documents. Only flag drift you can show evidence for. Read the relevant Juno courses, quizzes and journeys, compare each claim to the source, and give me a table: course, what it says, what the source says now, severity, suggested fix. This is a review, not an edit: change nothing yet. Offer to draft updated versions of the top items; after I approve, save them as drafts and don’t publish until I say so.
