The exposure your executives can act on
One combined view, organized around the questions your board asks.
When a rule changes, Juno trains the people it affects and keeps the proof.
Trusted by teams at
A regulator's email starts the clock, and the follow-up three days later asks for more than a number.
Legal updated the data-retention policy. Roll it out to everyone it applies to, with a check and an acknowledgment.
Data retention policy
What changed, a short check, and an acknowledgment.
Analytics
This quarterWe are ISO/IEC 27001 certified, and what we hold, with its status, is listed on the Trust Center.
An auditor asks which published version of the rule this person received, and how they answered questions about it afterward. Both are on the learner's record, alongside the certification your rule awarded and its issue date.
You've completed Information security refresher v3
Open answers are graded by a person, by the agent, or by both.
You define them, your rules award them, and they carry an expiration date.
Each record shows the type of proof used to complete it.
Filter once, save the view, and export the results.
Bulk upload certificates earned elsewhere and keep them in the same roster.
Every certification shows its issue date, expiration date, issuing authority, and number.
A new hire appears in the HRIS, someone moves into a supervisory role, or a recertification cycle comes around. An assignment rule already watches for each of these and assigns only the training that person needs.
All Users who match Role: Supervisor Location: EMEA Employment: Permanent must retake Information security refresher every 12 months.
If a person matches all of the criteria, assign Information security refresher, due 30 days after it is assigned.
Combine role, department, location, and employment type.
When someone matches the criteria, completes something, or hasn't started.
Assign, assign the next item, send a survey, or reassign on a recurring schedule.
The renewal cycle runs as a rule with its own recurring schedule.
See how many people a rule will touch before anything goes out.
Every run is logged, so you can see when a rule did nothing.
Set a fixed date, or count forward from the day the item was assigned.
A quiz at the end of a session tells you what someone answered that day. A check three weeks later, and a scenario graded by a validator, tell you what is still there when nobody is watching.
Time counts only while someone is working. After ten minutes without input, the clock stops, so the recorded time reflects real activity.
Information security refresher
The retention check: three weeks after the session, as its own step.
Ask about the same obligation again weeks after the session, as a separate step.
Open questions that ask what the person would do.
Set the passing score, the number of attempts, and the time limit.
Failed attempts stay on the record beside the one that passed.
Use a separate acknowledgment step, or let a graded quiz count as one, depending on your compliance requirements.
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.
Completion is the floor these teams cleared. What they talk about is everything around it.
“Running our compliance season with Juno was smooth, structured, and highly effective. Everything from automated assignments and reminders to manager visibility and real-time dashboards was planned in advance and executed flawlessly. We achieved over 90% completion across the company, and the process felt completely under control from start to finish.”
“Automated course assignments, reminders, and escalation flows based on role, legal mandates, and business needs.”
Trained thousands on key topics including compliance (5,200), information security (4,885), financial monitoring (~5,400) and personal safety (5,981).
76% employees rated Juno 9 or 10.
“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.”
“Coverage & Consistency: Centralized learning and compliance processes, enabling continuous updates as regulations evolve and ensuring uniform standards across all teams.”
Saved an estimated $20-30K annually by automating training administration and compliance tracking.
Reduced manual work, saving trainers 60-84 hours each year to reinvest in strategic initiatives.
One combined view, organized around the questions your board asks.
One population, this quarter
by role, region, and risk profile
days from publication to current
weeks after the session, by obligation
who approved each one, and when
Since the last rule change Republished Feb 4 · all affected people up to date by Feb 27
What the retention checks returned Information security refresher · re-asked Feb 27 · the open answers are with a validator for grading
Exceptions signed off
A combined view of one population: who is up to date by role and region, response time, retention results, and signed-off exceptions.