When to use proofs
Where to find it
Go to Admin → Budget → Credit Policies → Proofs.The Credit Policies tab is hidden by default. If you don’t see it, contact your Juno account team to turn it on for your organization.
Proof options
A proof is made of one or more options. Each option can be added once.Every option you add is required. Learners can’t submit until they’ve completed all of them, so add only what you actually need.
Create a proof
1
Open the Proofs tab
Go to Admin → Budget → Credit Policies and select Proofs, then select Create Proof.
2
Name the proof
Enter a Title and an optional Description. Learners see the title at the top of the submission dialog, so make it clear — for example Certificate of completion.
3
Choose the options
Under Options, select each type of evidence learners must provide: Upload File, Signature, Duration, or Free Text.
4
Confirm the trigger
Under Triggers, External Content Completion is selected. The proof is requested when a learner marks external learning as complete.
5
Choose who it applies to
Under Filters, keep All Users on, or turn it off and narrow the audience by groups, dates such as hire date, or user attributes such as department or location.
6
Save and activate
Save the proof, then turn on the Active switch in its row. New proofs are created inactive, so learners won’t be asked for anything until you activate it.
- One proof per learner. If more than one active proof matches a learner, only one of them is used. Keep the filters of active proofs from overlapping so each learner matches exactly one.
- Applies to all external learning. A proof isn’t tied to specific content — it’s requested for every external learning item the matching learners complete.
What learners see
When a learner who matches an active proof sets external learning to Completed — from My Learning, the home page, the catalog, or the content page — a dialog opens instead of completing immediately. The dialog shows the proof title, a Pending Validation label, and a progress count of the steps completed. The learner fills in each option and selects Submit and Mark as Complete. The learning is marked complete and the proof is saved at the same time. If they cancel, the learning stays incomplete.No approval step. The Pending Validation label is informational — there is no approve or reject workflow. The completion is recorded as soon as the learner submits. To validate evidence, review submissions in Learning Management (below) and follow up with learners directly.
Review submitted proofs
Submitted proofs appear in Admin → Content → Learning Management, in the External Learning Fields column group:
View Proof opens the proof details: submission date, reported duration, the uploaded file with a Download button, the text response, and the signature.
Build an audit view
1
Show the proof columns
In Learning Management, turn on the External Learning Fields column group.
2
Filter to the audit scope
Filter by date range, department, or other user attributes, then filter Proof Type to the evidence the auditor expects — for example Manual Proof Upload and Digital Signature.
3
Save and export
Save the view so you can reuse it for the next audit, then export to CSV. The export includes Proof, Proof Type, Proof File (file name and link), and Proof Submitted At for every row.
Manage proofs
From the Proofs table you can:- Edit a proof’s title, description, options, or filters. Changes apply to future submissions only.
- Activate or deactivate a proof with the Active switch. Deactivating stops new requests; existing submissions are kept.
- Delete a proof. You’re asked to confirm first.