/admin/1) is where you see how learning content is performing, manage activities across your org, and run external content, events, and certifications.
Most sub-tabs require an Admin or domain-admin role for Content (or Events for the Events tab). Some tabs additionally require the LMS or LXP module — see each section below.
Sub-tabs at a glance
Internal content analytics
Why use it: answer “how is our internal content performing, and where are people getting stuck?” Each row is a piece of content with a live snapshot of enrollment, completion, and progress distribution. Click a row to drill into per-learner analytics for that content item.
Enrollment-type filter
The All Enrollment Types dropdown (top right) changes which enrollments the rates count. This is the most-asked-about control on the page — it changes the meaning of every percentage.
These are filters over the same data (
assigned vs self is recorded on each usersUnit); they do not change anything on the content itself.
Status filter (Active vs Archived)
The Status dropdown next to it switches between two scopes:
- Active Units (default) — content that is live for learners.
- Archived Units — archived content. Stays in analytics but is hidden from learners’ academy view. Archive is reversible from the row’s action menu.
Employee filter
The Employees (N) button (top left) opens a multi-tab filter dialog so you can narrow the table to enrollments for specific cohorts of users. Tabs:
- Groups — pick one or more user groups.
- Users — pick individual users.
- Location, Department, Position — filter by user attributes.
Columns
Per-row actions
Learning management
Why use it: the most granular view in Juno — one row per learner and activity. Build saved views with custom columns and filters, roll the table up by department or unit, and export to CSV.
Managers see a scoped version of the same table at Managers → Content → Learning Management, automatically filtered to their direct reports — see Learning Activities (Managers).
External content management
Why use it: see what third-party content is actually being consumed by your org — what providers, what items, by whom. Useful for renewing licenses, curating the catalog, and chasing down spend. The table is scoped to external content with real activity (completed, in progress, recommended, or requested) — not the whole catalog.
Columns
Filters
Title (text), Provider (autocomplete), Type (autocomplete), Free/Paid. There’s also an Include Juno User switch — toggle to include/exclude the synthetic Juno test user.Per-row click
Opens the content detail dialog with engagement breakdown.Events management
Why use it: one table for every event in the org — instructor-led training, webinars, workshops — with attendees and sessions accessible from the same row.
Columns
Row expansion
Each row has a chevron on the right — expand to see sessions and attendees inline (sessions list, with start/end, location, instructors, RSVP status).Filters
Title, Type, Label, Creator, Members. Plus the Include Juno User switch.Certification management
Why use it: a roster of who holds which certificates, with bulk upload for legacy/external credentials and CSV export for HR / compliance. The page is titled Users Certifications.
Top-bar actions
Columns
Per-row click
Opens the user’s profile scoped to certificate analytics (their full certificate history). See also: Certifications for the learner-facing view, and Roles & Security for who can issue/revoke.Key behaviors and nuances
- Archive ≠ Delete. Archive is reversible and hides content from learners while keeping analytics. Delete (handled outside this view) is permanent.
- Drafts are visible to authors and admins only; they don’t appear to learners until published.
- Views and exports belong to the Learning Management table — see Views and Export to CSV.
- Enrollment-type filter changes the meaning of every percentage on the Internal Content tab — verify which mode you’re in before sharing a screenshot.
- The Include Juno User switch (off by default) controls whether the synthetic internal test user (
junojourney.comaccounts created for QA) is counted in the table — turn it on when validating QA setups, leave it off for real-org reporting.