Legal published data retention policy v3. Roll it out to everyone it applies to, with a check and an acknowledgment.
Data retention policy v3
What changed in v3, a 5-question check, and an acknowledgment.
Juno trains everyone a policy affects and collects each acknowledgment.
Analytics
Last 30 daysEmails, reminders, and a spreadsheet of who signed: every policy change turns into weeks of chasing.
Legal published data retention policy v3. Roll it out to everyone it applies to, with a check and an acknowledgment.
Data retention policy v3
What changed in v3, a 5-question check, and an acknowledgment.
Each learner's record names the published version of the course they saw.
The quiz result and attempts appear 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.
Each learner's record names the published version of the course they saw.
The quiz result and attempts appear 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.
CancelAssign to 1,652 peopleRole, department, location, or employee type decides who is covered.
Contractors are an employee type, so a rule can include or exclude them.
A dry run counts the people a rule will reach before anything is sent.
The compliance owner approves the scope before anyone is assigned.
For the people who join after this rollout: Company & Department-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.
Each change gets one of three priorities: Mission-critical; Important, not urgent; or Nice to know.
Your LLM reaches Confluence, Notion, SharePoint, or your GRC tool.
Last year's course is updated as a draft, then published as the new version.
Your model reads what changed between the two versions of the document.
Each change gets one of three priorities: Mission-critical; Important, not urgent; or Nice to know.
Your LLM reaches Confluence, Notion, SharePoint, or your GRC tool.
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 process works for a product release: Release & Product Update
If a person has not started their training after 7 days, send them a nudge.
If a person has not completed their training 7 days before their due date, send them a notification.
If a person has not completed their training 1 day before their due date, send them a notification.
If a person has not completed their training 2 days after their due date, send them a notification.
Notifications go out 7 days before, 1 day before, and 2 days after.
Two automation actions that run on rules you set, for anyone who hasn't started.
Each manager sees who on their team is overdue.
Each certification you create has its own expiration date and 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. Here is how it went, in their 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 the time from publication until everyone affected is up to date on this version.
A short course, a 5-question check, and an acknowledgment, with 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, gaps visible before the deadline.
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.