> ## Documentation Index
> Fetch the complete documentation index at: https://docs.junojourney.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proof of completion

> Require learners to submit evidence (a certificate, signature, duration, or written response) when they complete external learning, and use it for audits.

export const RelatedPages = ({pages = []}) => {
  if (pages.length === 0) return null;
  return <>
      <br />
      <strong>Related articles</strong>
      <CardGroup cols={2}>
        {pages.map(page => <Card title={page.title} href={page.href} key={page.href} />)}
      </CardGroup>
    </>;
};

export const Prerequisites = ({items = []}) => {
  return <Note title="Before you start">
      {items.length > 0 && <ul>
          {items.map((item, index) => <li key={index}>{item}</li>)}
        </ul>}
    </Note>;
};

export const RoleBadge = ({roles = []}) => {
  const colorMap = {
    Admin: "yellow",
    Manager: "blue",
    Learner: "green",
    "Co-editor": "purple"
  };
  return <>
      {roles.map(role => <span key={role}><Badge color={colorMap[role] || "gray"} size="sm" shape="pill">{role}</Badge>{" "}</span>)}
    </>;
};

export const FeatureAvailability = ({module, feature}) => {
  const label = feature || module;
  return <Info title="Feature availability">
      {label ? <>This feature requires the <strong>{label}</strong> module. </> : <>This feature may not be enabled for your organization. </>}
      If you don't see it in Juno, contact your administrator.
    </Info>;
};

<RoleBadge roles={["Admin"]} />

<FeatureAvailability />

Proofs let you define what evidence learners must provide when they mark external learning as complete — a certificate upload, a signature, the hours spent, or a written response. Every submission is stored with the learning activity, so you can review it, download it, and export it for audits.

***

## When to use proofs

| Use case | What to collect | Why it helps |
| - | - | - |
| **Regulatory and quality audits** (for example Qualiopi, ISO, or sector regulators) | Upload file + Signature | Auditors ask for evidence that training actually happened. Each completion carries a certificate and a signed attestation, exportable in one CSV. |
| **Continuing education (CPD / CPE) hours** | Duration + Upload file | Learners report the hours they spent and attach the provider's certificate, giving you a defensible record of credited hours. |
| **Certification verification** | Upload file | Confirm that learners who completed a paid certification actually passed it before you count it toward compliance or skills records. |
| **Justifying learning spend** | Upload file + Duration | When learning is funded through budget or credits, the proof shows the money produced a completed course. |
| **Learner reflection and course quality** | Free text | Collect a short review of each external course to decide which providers to keep in the catalog. |

***

## Where to find it

Go to **Admin → Budget → Credit Policies → Proofs**.

<Note>
  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.
</Note>

***

## Proof options

A proof is made of one or more options. Each option can be added once.

| Option | What the learner provides |
| - | - |
| **Upload file** | A file confirming completion — typically a certificate, but a screenshot works too. Any file type is accepted. |
| **Signature** | A signature drawn directly in the dialog, attesting that they completed the learning. |
| **Duration** | The number of hours the learning took. |
| **Free text** | A written response — for example a review of the course or a summary of what they learned. |

<Note>
  Every option you add is required. Learners can't submit until they've completed all of them, so add only what you actually need.
</Note>

***

## Create a proof

<Prerequisites
  items={[
"Admin access to Admin → Budget → Credit Policies",
"External learning available to your learners (catalog, external providers, or requests)",
]}
/>

<Steps>
  <Step title="Open the Proofs tab">
    Go to **Admin → Budget → Credit Policies** and select **Proofs**, then select **Create Proof**.
  </Step>

  <Step title="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*.
  </Step>

  <Step title="Choose the options">
    Under **Options**, select each type of evidence learners must provide: **Upload File**, **Signature**, **Duration**, or **Free Text**.
  </Step>

  <Step title="Confirm the trigger">
    Under **Triggers**, **External Content Completion** is selected. The proof is requested when a learner marks external learning as complete.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Note>
  * **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.
</Note>

***

## 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.

<Note>
  **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.
</Note>

***

## Review submitted proofs

Submitted proofs appear in **Admin → Content → Learning Management**, in the **External Learning Fields** column group:

| Column | What it shows |
| - | - |
| **Proof** | Yes / No — whether the activity has any proof. |
| **Proof Type** | How completion was evidenced, for example *Manual Proof Upload* or *Digital Signature*. An activity can have several. |
| **Proof File** | Select **View Proof** to open the proof details. Shows *Signature only* when no file was uploaded. |
| **Proof Submitted At** | When the learner submitted the proof. |

**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

<Steps>
  <Step title="Show the proof columns">
    In **Learning Management**, turn on the **External Learning Fields** column group.
  </Step>

  <Step title="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*.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Tip>
  Proof Type also covers learning tracked by Juno itself — **Platform-Tracked Completion** for content completed in Juno, and **Sync via Zoom / Teams / Google Meet Integration** for event attendance. Including those values gives auditors a single evidence trail for internal and external learning.
</Tip>

See [Learning Management](/admin/learning-management) for saved views, filters, and exports.

***

## 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.

***

<RelatedPages
  pages={[
{ href: "/admin/learning-management", title: "Learning Management" },
{ href: "/admin/budget-and-credits", title: "Budget & Credits" },
{ href: "/admin/automations", title: "Automations" },
{ href: "/learning/external-providers", title: "External Learning Sources" },
]}
/>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.