mobieusKnow mobieusLearn admin guide History #362

Revision #362

Approved
All revisions
Author
system
Submitted
Jun 14, 2026 8:27pm
Summary
Add Video lessons section (course video, Phase 2.1)
# mobieusLearn admin guide
The full reference for `/admin/learn` on your tenant. Every nav section, every surface, and how to use them. Sign in as a tenant administrator and open `/admin/learn` to follow along.
## What's here
mobieusLearn is the learning management system built into your Mobieus community. It runs as the admin surface at `/admin/learn` and a learner surface at `/learn/my`. Authors build courses; the catalog is at `/learn/courses`; certificates and badges are minted automatically when learners complete; everything is verifiable.
The admin nav groups every capability under six headings. Each section below is one heading.
## Catalog — courses, categories, tags, paths
The Catalog group owns the public-facing course library at `/learn/courses`. Four surfaces:
**Courses** (`/admin/learn/courses`) — the course → module → lesson → activity tree. Each course has versions, an analytics drill-down, and a review-gate workflow. Click any course to open the authoring canvas. Status transitions: draft → in review → published → archived.
**Categories** (`/admin/learn/categories`) — subject hierarchy that backs the catalog filter. Categories nest one level deep. Two-letter slugs work but full words index better for SEO.
**Tags** (`/admin/learn/tags`) — free-form labels that work alongside categories. Tags drive the automation engine (a tag matching a learning-path rule auto-enrolls the learner), so name them with care.
**Learning paths** (`/admin/learn/paths`) — sequence courses into an objective-aligned journey. Paths can require courses in order or leave them free-order; gating rules support "must complete X before Y unlocks".
## Authoring — roles, templates, packages, LTI
**Roles & team** (`/admin/learn/roles`) — grant Learn capabilities to specific tenant users. Six roles ship: viewer, author, reviewer, instructor, curriculum architect, learn admin. The first column lists every user who already has a Learn role; the second column is "non-Learn users you can promote".
**Module templates** (`/admin/learn/templates`) — Gagné-scaffolded starting points. Each template seeds a module with placeholder lessons matching one of the nine events of instruction. Use templates to keep instructional design consistent across authors.
**SCORM packages** (`/admin/learn/scorm`) — upload SCORM 1.2 or SCORM 2004 archives. The runtime serves them inside an iframe and tracks completion via the SCORM API. Use this when you have existing content from Articulate, Captivate, or any SCORM authoring tool.
**cmi5 packages** (`/admin/learn/cmi5-packages`) — modern, xAPI-native replacement for SCORM. Reports completion verbs to the tenant's internal LRS and forwards them via the outbound xAPI bridge. Prefer cmi5 for new content where the authoring tool supports it.
**LTI 1.3** (`/admin/learn/lti-platforms`) — register external LMS platforms (Canvas, Brightspace, Blackboard, Schoology, and other LTI 1.3 platforms) as launch sources. Each tenant ships with an RSA-2048 tool keypair generated at provision. Paste the platform's metadata into the form; the platform admin pastes your JWKS URL into theirs; launches work both directions.
## Delivery — cohorts, enrollments, certificates, badges
**Cohorts** (`/admin/learn/cohorts`) — group enrollment + org reporting. A cohort holds a list of learners, optional start/end dates, optional enrollment cap, and a course or learning path it grants access to. Use cohorts for B2B sales (one cohort per buyer org), trainer-led batches, or any group that needs to be reported on together.
**Enrollments** (`/admin/learn/enrollments`) — individual learner access. Most enrollments are automatic (purchase, cohort grant, learning-path completion), but admins can manually enroll a user from this surface. Each enrollment shows progress percentage, last activity, and an entitlement window if one applies.
**Certificates** (`/admin/learn/certificates`) — every issued credential. Filter by course or learner. Each row shows status (issued / revoked) and links to the public verification URL. The Revoke action is reversible.
**Cert templates** (`/admin/learn/cert-templates`) — brand the certificate PDF. Each template controls logo, accent color, signature image, footer text, and credit-hour formatting. One template is the default for new courses; override per course via the course settings.
**Open Badges** (`/admin/learn/badges`) — Open Badges 3.0 credentials. Badges are signed with Ed25519 (RFC 8032) and verifiable at the public issuer page `/learn/badges/issuer`. Mint a badge by giving it a slug, a name, a description, an image URL, and a criteria narrative. Award rules live on each badge.
## Assessments — assessments, question bank, pools
**Assessments** (`/admin/learn/assessments`) — quizzes and tests built from items and pools. Each assessment carries scoring (% to pass), attempt limits, time limits, and feedback rules.
**Question bank** (`/admin/learn/questions`) — reusable items tagged by objective, Bloom level, and difficulty. The bank is shared across every assessment on the tenant. Use the AI-generate button on the bank to draft items from a learning objective; review before accepting.
+ **Pools** (`/admin/learn/pools`) — randomization sets. A pool draws N items from the bank matching tag filters, so every learner sees a different mix. Use pools for high-stakes tests where you need fresh items per attempt.
− **Pools** (`/admin/learn/pools`) — randomization sets. A pool holds a set of questions you choose; an assessment draws N of them at random on every attempt, so every learner sees a different mix and no two sittings are alike. Use pools for high-stakes tests where you need fresh items per attempt.
## Grading and lesson Q&A — the teaching surfaces
**Grading inbox** (`/learn/teach/grading`) — essay and file-upload answers can't be auto-scored, so they land here as "awaiting grade." Open a submission, read the response (or download the file), enter a score, and add feedback. The score is clamped to the question's maximum, and the learner's attempt result recomputes the moment you save — so an assignment is no longer stuck at zero waiting on a human. The inbox shows only courses you're on the team for, and grading requires the grade-submissions capability.
**Lesson Q&A** (`/learn/teach/questions`) — every lesson has a questions area where learners ask and anyone can reply. This view collects every question across your courses that has no accepted answer yet, so nothing falls through. On the lesson itself, you (or any replier) can mark the reply that answered the question; the asker and the lesson both show it as resolved.
## Analytics — dashboards, item analysis, AI usage
**Dashboards** (`/admin/learn/analytics`) — three views: learner (one row per learner with completion + score summaries), instructor (one row per course-author pair), admin (cross-course rollups). All views read from the rollup tables, so they serve fast even with millions of xAPI statements.
**Item analysis** (`/admin/learn/item-analysis`) — flags items the statistics say are weak: too easy, too hard, low discrimination, distractor under-pick. The threshold (minimum attempts before stats appear) is editable inline; the default is 30. Raise the threshold for low-volume courses, lower it for high-volume ones.
**AI usage** (`/admin/learn/ai-usage`) — Anthropic token spend per feature for the trailing 30 days. Tracks question-generation, lesson-takeaway, and course-description calls separately so you can see which features are pulling weight.
## Integrations — SCIM, outbound xAPI
**SCIM 2.0** (`/admin/learn/scim-credentials`) — inbound user/group provisioning from an enterprise IdP. Generate a bearer token, paste it into Okta / Entra ID / Workday / Ping / JumpCloud, and users + groups push in automatically. Group memberships map to mobieusLearn cohorts on the way through. See the [SCIM 2.0 IdP setup guide](/know/learn-scim-setup) for step-by-step setup.
**Outbound xAPI** (`/admin/learn/xapi-outbound`) — forward every xAPI statement to an external Learning Record Store. Configure endpoint + Basic auth, hit Test, save. Statements mirror in real time; the worker retries on transient failures.
## Audit log + Settings
**Audit log** (`/admin/learn/audit`) — every admin action that mutated learn state. Filter by actor, event type, or date range. Use this when investigating "who changed what when".
**Settings** (`/admin/learn/settings`) — the home for tenant-wide Learn configuration:
- **Open Badges issuer** card — shows whether the Ed25519 signing key is provisioned. If not, click "Provision issuer keypair" and the system generates one.
- **mobieusAI authoring** card — paste an Anthropic API key to enable AI-assisted course authoring. The key is stored on this tenant only. Use "Rotate or remove" to change it. (The community-wide AI control plane — master switch, spend caps, and the AI helpers outside authoring — lives at `/admin/ai`.)
- **Native xAPI LRS** card — informational only; every statement lives in the tenant's own database.
- **Item analysis threshold** card — links to the inline editor on the item-analysis page.
## Video lessons
Add a video straight into a lesson. In the course canvas, add an activity and set its kind to **Video**, save it, then upload the file on the activity's edit screen. Mobieus prepares the video for smooth playback that adapts to each viewer's connection and device, and the lesson plays it inline — no separate video host and no encoding settings to fiddle with.
- **Formats** — MP4, MOV, WebM, or MKV.
- **Length** — your plan sets the longest video you can upload: 30 minutes on Pro, 2 hours on Creator Plus, and no limit on Sovereign. A file over the limit is rejected with a clear message after it uploads.
- **Processing** — right after you upload, the video shows as processing for a few minutes while it is prepared, then flips to ready. Replace the file at any time from the same panel.
- **Completion** — set the activity's completion criteria to **Viewed**. Finishing the video (or the learner clicking Mark complete) completes the lesson, and learners resume right where they left off.
Course video is included on Pro, Creator Plus, and Sovereign.
## Common workflows
**Launch a course end-to-end**
1. Create a category if you need one.
2. New course under that category, draft state.
3. Add modules + lessons inside the course; populate activities (video, reading, assessment).
4. Build a cert template (or accept the default) and attach it to the course.
5. Optionally create a badge tied to course completion.
6. Submit course for review; reviewer approves; status flips to published.
7. Either sell it via mobieusCore (Products → New course), grant via cohort, or open enrollment to all members.
**Bring an organization's roster in via SCIM**
1. Settings → confirm Open Badges issuer is provisioned (needed for credential signing).
2. SCIM 2.0 page → New credential → Pick a name → Copy the bearer token (shown once).
3. In the IdP, point SCIM at `https://<your-tenant>.mobieus.io/scim/v2/` and paste the token.
4. Map IdP groups to mobieusLearn cohorts using the cohort-name suffix convention (see the [SCIM guide](/know/learn-scim-setup)).
5. Watch the IdP push the initial roster; subsequent changes flow on the IdP's SCIM cadence.
**Wire up an external LMS to launch into a mobieusLearn course**
1. Authoring → LTI 1.3 → copy your tool's JWKS URL + Login Initiation URL + Redirect URI.
2. In the external LMS, register Mobieus as a new LTI 1.3 tool with those URLs.
3. The external LMS gives you a Platform Issuer + Client ID + Deployment ID + Platform JWKS URL.
4. Back in mobieusLearn, paste those values into the New platform form.
5. Add a course as a launchable resource; the platform's instructors can now embed it.
## What's NOT in this guide
Per-learner experience (the `/learn/my` dashboard, course consumption, assessment-taking, the credential wallet) is covered in the [learner dashboard guide](/know/mobieuslearn-learner-guide). This guide is for admins.
## Related articles
- [Your learning dashboard](/know/mobieuslearn-learner-guide)
- [mobieusLearn SCIM 2.0 — IdP setup guide](/know/learn-scim-setup)
- [mobieusCore API — mobieusLearn](/know/api-learn)

mobieusLearn admin guide

The full reference for /admin/learn on your tenant. Every nav section, every surface, and how to use them. Sign in as a tenant administrator and open /admin/learn to follow along.

What's here

mobieusLearn is the learning management system built into your Mobieus community. It runs as the admin surface at /admin/learn and a learner surface at /learn/my. Authors build courses; the catalog is at /learn/courses; certificates and badges are minted automatically when learners complete; everything is verifiable.

The admin nav groups every capability under six headings. Each section below is one heading.

Catalog — courses, categories, tags, paths

The Catalog group owns the public-facing course library at /learn/courses. Four surfaces:

Courses (/admin/learn/courses) — the course → module → lesson → activity tree. Each course has versions, an analytics drill-down, and a review-gate workflow. Click any course to open the authoring canvas. Status transitions: draft → in review → published → archived.

Categories (/admin/learn/categories) — subject hierarchy that backs the catalog filter. Categories nest one level deep. Two-letter slugs work but full words index better for SEO.

Tags (/admin/learn/tags) — free-form labels that work alongside categories. Tags drive the automation engine (a tag matching a learning-path rule auto-enrolls the learner), so name them with care.

Learning paths (/admin/learn/paths) — sequence courses into an objective-aligned journey. Paths can require courses in order or leave them free-order; gating rules support "must complete X before Y unlocks".

Authoring — roles, templates, packages, LTI

Roles & team (/admin/learn/roles) — grant Learn capabilities to specific tenant users. Six roles ship: viewer, author, reviewer, instructor, curriculum architect, learn admin. The first column lists every user who already has a Learn role; the second column is "non-Learn users you can promote".

Module templates (/admin/learn/templates) — Gagné-scaffolded starting points. Each template seeds a module with placeholder lessons matching one of the nine events of instruction. Use templates to keep instructional design consistent across authors.

SCORM packages (/admin/learn/scorm) — upload SCORM 1.2 or SCORM 2004 archives. The runtime serves them inside an iframe and tracks completion via the SCORM API. Use this when you have existing content from Articulate, Captivate, or any SCORM authoring tool.

cmi5 packages (/admin/learn/cmi5-packages) — modern, xAPI-native replacement for SCORM. Reports completion verbs to the tenant's internal LRS and forwards them via the outbound xAPI bridge. Prefer cmi5 for new content where the authoring tool supports it.

LTI 1.3 (/admin/learn/lti-platforms) — register external LMS platforms (Canvas, Brightspace, Blackboard, Schoology, and other LTI 1.3 platforms) as launch sources. Each tenant ships with an RSA-2048 tool keypair generated at provision. Paste the platform's metadata into the form; the platform admin pastes your JWKS URL into theirs; launches work both directions.

Delivery — cohorts, enrollments, certificates, badges

Cohorts (/admin/learn/cohorts) — group enrollment + org reporting. A cohort holds a list of learners, optional start/end dates, optional enrollment cap, and a course or learning path it grants access to. Use cohorts for B2B sales (one cohort per buyer org), trainer-led batches, or any group that needs to be reported on together.

Enrollments (/admin/learn/enrollments) — individual learner access. Most enrollments are automatic (purchase, cohort grant, learning-path completion), but admins can manually enroll a user from this surface. Each enrollment shows progress percentage, last activity, and an entitlement window if one applies.

Certificates (/admin/learn/certificates) — every issued credential. Filter by course or learner. Each row shows status (issued / revoked) and links to the public verification URL. The Revoke action is reversible.

Cert templates (/admin/learn/cert-templates) — brand the certificate PDF. Each template controls logo, accent color, signature image, footer text, and credit-hour formatting. One template is the default for new courses; override per course via the course settings.

Open Badges (/admin/learn/badges) — Open Badges 3.0 credentials. Badges are signed with Ed25519 (RFC 8032) and verifiable at the public issuer page /learn/badges/issuer. Mint a badge by giving it a slug, a name, a description, an image URL, and a criteria narrative. Award rules live on each badge.

Assessments — assessments, question bank, pools

Assessments (/admin/learn/assessments) — quizzes and tests built from items and pools. Each assessment carries scoring (% to pass), attempt limits, time limits, and feedback rules.

Question bank (/admin/learn/questions) — reusable items tagged by objective, Bloom level, and difficulty. The bank is shared across every assessment on the tenant. Use the AI-generate button on the bank to draft items from a learning objective; review before accepting.

Pools (/admin/learn/pools) — randomization sets. A pool draws N items from the bank matching tag filters, so every learner sees a different mix. Use pools for high-stakes tests where you need fresh items per attempt.

Grading and lesson Q&A — the teaching surfaces

Grading inbox (/learn/teach/grading) — essay and file-upload answers can't be auto-scored, so they land here as "awaiting grade." Open a submission, read the response (or download the file), enter a score, and add feedback. The score is clamped to the question's maximum, and the learner's attempt result recomputes the moment you save — so an assignment is no longer stuck at zero waiting on a human. The inbox shows only courses you're on the team for, and grading requires the grade-submissions capability.

Lesson Q&A (/learn/teach/questions) — every lesson has a questions area where learners ask and anyone can reply. This view collects every question across your courses that has no accepted answer yet, so nothing falls through. On the lesson itself, you (or any replier) can mark the reply that answered the question; the asker and the lesson both show it as resolved.

Analytics — dashboards, item analysis, AI usage

Dashboards (/admin/learn/analytics) — three views: learner (one row per learner with completion + score summaries), instructor (one row per course-author pair), admin (cross-course rollups). All views read from the rollup tables, so they serve fast even with millions of xAPI statements.

Item analysis (/admin/learn/item-analysis) — flags items the statistics say are weak: too easy, too hard, low discrimination, distractor under-pick. The threshold (minimum attempts before stats appear) is editable inline; the default is 30. Raise the threshold for low-volume courses, lower it for high-volume ones.

AI usage (/admin/learn/ai-usage) — Anthropic token spend per feature for the trailing 30 days. Tracks question-generation, lesson-takeaway, and course-description calls separately so you can see which features are pulling weight.

Integrations — SCIM, outbound xAPI

SCIM 2.0 (/admin/learn/scim-credentials) — inbound user/group provisioning from an enterprise IdP. Generate a bearer token, paste it into Okta / Entra ID / Workday / Ping / JumpCloud, and users + groups push in automatically. Group memberships map to mobieusLearn cohorts on the way through. See the SCIM 2.0 IdP setup guide for step-by-step setup.

Outbound xAPI (/admin/learn/xapi-outbound) — forward every xAPI statement to an external Learning Record Store. Configure endpoint + Basic auth, hit Test, save. Statements mirror in real time; the worker retries on transient failures.

Audit log + Settings

Audit log (/admin/learn/audit) — every admin action that mutated learn state. Filter by actor, event type, or date range. Use this when investigating "who changed what when".

Settings (/admin/learn/settings) — the home for tenant-wide Learn configuration:

  • Open Badges issuer card — shows whether the Ed25519 signing key is provisioned. If not, click "Provision issuer keypair" and the system generates one.
  • mobieusAI authoring card — paste an Anthropic API key to enable AI-assisted course authoring. The key is stored on this tenant only. Use "Rotate or remove" to change it. (The community-wide AI control plane — master switch, spend caps, and the AI helpers outside authoring — lives at /admin/ai.)
  • Native xAPI LRS card — informational only; every statement lives in the tenant's own database.
  • Item analysis threshold card — links to the inline editor on the item-analysis page.

Video lessons

Add a video straight into a lesson. In the course canvas, add an activity and set its kind to Video, save it, then upload the file on the activity's edit screen. Mobieus prepares the video for smooth playback that adapts to each viewer's connection and device, and the lesson plays it inline — no separate video host and no encoding settings to fiddle with.

  • Formats — MP4, MOV, WebM, or MKV.
  • Length — your plan sets the longest video you can upload: 30 minutes on Pro, 2 hours on Creator Plus, and no limit on Sovereign. A file over the limit is rejected with a clear message after it uploads.
  • Processing — right after you upload, the video shows as processing for a few minutes while it is prepared, then flips to ready. Replace the file at any time from the same panel.
  • Completion — set the activity's completion criteria to Viewed. Finishing the video (or the learner clicking Mark complete) completes the lesson, and learners resume right where they left off.

Course video is included on Pro, Creator Plus, and Sovereign.

Common workflows

Launch a course end-to-end

  1. Create a category if you need one.
  2. New course under that category, draft state.
  3. Add modules + lessons inside the course; populate activities (video, reading, assessment).
  4. Build a cert template (or accept the default) and attach it to the course.
  5. Optionally create a badge tied to course completion.
  6. Submit course for review; reviewer approves; status flips to published.
  7. Either sell it via mobieusCore (Products → New course), grant via cohort, or open enrollment to all members.

Bring an organization's roster in via SCIM

  1. Settings → confirm Open Badges issuer is provisioned (needed for credential signing).
  2. SCIM 2.0 page → New credential → Pick a name → Copy the bearer token (shown once).
  3. In the IdP, point SCIM at https://<your-tenant>.mobieus.io/scim/v2/ and paste the token.
  4. Map IdP groups to mobieusLearn cohorts using the cohort-name suffix convention (see the SCIM guide).
  5. Watch the IdP push the initial roster; subsequent changes flow on the IdP's SCIM cadence.

Wire up an external LMS to launch into a mobieusLearn course

  1. Authoring → LTI 1.3 → copy your tool's JWKS URL + Login Initiation URL + Redirect URI.
  2. In the external LMS, register Mobieus as a new LTI 1.3 tool with those URLs.
  3. The external LMS gives you a Platform Issuer + Client ID + Deployment ID + Platform JWKS URL.
  4. Back in mobieusLearn, paste those values into the New platform form.
  5. Add a course as a launchable resource; the platform's instructors can now embed it.

What's NOT in this guide

Per-learner experience (the /learn/my dashboard, course consumption, assessment-taking, the credential wallet) is covered in the learner dashboard guide. This guide is for admins.

Related articles

# mobieusLearn admin guide

The full reference for `/admin/learn` on your tenant. Every nav section, every surface, and how to use them. Sign in as a tenant administrator and open `/admin/learn` to follow along.

## What's here

mobieusLearn is the learning management system built into your Mobieus community. It runs as the admin surface at `/admin/learn` and a learner surface at `/learn/my`. Authors build courses; the catalog is at `/learn/courses`; certificates and badges are minted automatically when learners complete; everything is verifiable.

The admin nav groups every capability under six headings. Each section below is one heading.

## Catalog — courses, categories, tags, paths

The Catalog group owns the public-facing course library at `/learn/courses`. Four surfaces:

**Courses** (`/admin/learn/courses`) — the course → module → lesson → activity tree. Each course has versions, an analytics drill-down, and a review-gate workflow. Click any course to open the authoring canvas. Status transitions: draft → in review → published → archived.

**Categories** (`/admin/learn/categories`) — subject hierarchy that backs the catalog filter. Categories nest one level deep. Two-letter slugs work but full words index better for SEO.

**Tags** (`/admin/learn/tags`) — free-form labels that work alongside categories. Tags drive the automation engine (a tag matching a learning-path rule auto-enrolls the learner), so name them with care.

**Learning paths** (`/admin/learn/paths`) — sequence courses into an objective-aligned journey. Paths can require courses in order or leave them free-order; gating rules support "must complete X before Y unlocks".

## Authoring — roles, templates, packages, LTI

**Roles & team** (`/admin/learn/roles`) — grant Learn capabilities to specific tenant users. Six roles ship: viewer, author, reviewer, instructor, curriculum architect, learn admin. The first column lists every user who already has a Learn role; the second column is "non-Learn users you can promote".

**Module templates** (`/admin/learn/templates`) — Gagné-scaffolded starting points. Each template seeds a module with placeholder lessons matching one of the nine events of instruction. Use templates to keep instructional design consistent across authors.

**SCORM packages** (`/admin/learn/scorm`) — upload SCORM 1.2 or SCORM 2004 archives. The runtime serves them inside an iframe and tracks completion via the SCORM API. Use this when you have existing content from Articulate, Captivate, or any SCORM authoring tool.

**cmi5 packages** (`/admin/learn/cmi5-packages`) — modern, xAPI-native replacement for SCORM. Reports completion verbs to the tenant's internal LRS and forwards them via the outbound xAPI bridge. Prefer cmi5 for new content where the authoring tool supports it.

**LTI 1.3** (`/admin/learn/lti-platforms`) — register external LMS platforms (Canvas, Brightspace, Blackboard, Schoology, and other LTI 1.3 platforms) as launch sources. Each tenant ships with an RSA-2048 tool keypair generated at provision. Paste the platform's metadata into the form; the platform admin pastes your JWKS URL into theirs; launches work both directions.

## Delivery — cohorts, enrollments, certificates, badges

**Cohorts** (`/admin/learn/cohorts`) — group enrollment + org reporting. A cohort holds a list of learners, optional start/end dates, optional enrollment cap, and a course or learning path it grants access to. Use cohorts for B2B sales (one cohort per buyer org), trainer-led batches, or any group that needs to be reported on together.

**Enrollments** (`/admin/learn/enrollments`) — individual learner access. Most enrollments are automatic (purchase, cohort grant, learning-path completion), but admins can manually enroll a user from this surface. Each enrollment shows progress percentage, last activity, and an entitlement window if one applies.

**Certificates** (`/admin/learn/certificates`) — every issued credential. Filter by course or learner. Each row shows status (issued / revoked) and links to the public verification URL. The Revoke action is reversible.

**Cert templates** (`/admin/learn/cert-templates`) — brand the certificate PDF. Each template controls logo, accent color, signature image, footer text, and credit-hour formatting. One template is the default for new courses; override per course via the course settings.

**Open Badges** (`/admin/learn/badges`) — Open Badges 3.0 credentials. Badges are signed with Ed25519 (RFC 8032) and verifiable at the public issuer page `/learn/badges/issuer`. Mint a badge by giving it a slug, a name, a description, an image URL, and a criteria narrative. Award rules live on each badge.

## Assessments — assessments, question bank, pools

**Assessments** (`/admin/learn/assessments`) — quizzes and tests built from items and pools. Each assessment carries scoring (% to pass), attempt limits, time limits, and feedback rules.

**Question bank** (`/admin/learn/questions`) — reusable items tagged by objective, Bloom level, and difficulty. The bank is shared across every assessment on the tenant. Use the AI-generate button on the bank to draft items from a learning objective; review before accepting.

**Pools** (`/admin/learn/pools`) — randomization sets. A pool draws N items from the bank matching tag filters, so every learner sees a different mix. Use pools for high-stakes tests where you need fresh items per attempt.

## Grading and lesson Q&A — the teaching surfaces

**Grading inbox** (`/learn/teach/grading`) — essay and file-upload answers can't be auto-scored, so they land here as "awaiting grade." Open a submission, read the response (or download the file), enter a score, and add feedback. The score is clamped to the question's maximum, and the learner's attempt result recomputes the moment you save — so an assignment is no longer stuck at zero waiting on a human. The inbox shows only courses you're on the team for, and grading requires the grade-submissions capability.

**Lesson Q&A** (`/learn/teach/questions`) — every lesson has a questions area where learners ask and anyone can reply. This view collects every question across your courses that has no accepted answer yet, so nothing falls through. On the lesson itself, you (or any replier) can mark the reply that answered the question; the asker and the lesson both show it as resolved.

## Analytics — dashboards, item analysis, AI usage

**Dashboards** (`/admin/learn/analytics`) — three views: learner (one row per learner with completion + score summaries), instructor (one row per course-author pair), admin (cross-course rollups). All views read from the rollup tables, so they serve fast even with millions of xAPI statements.

**Item analysis** (`/admin/learn/item-analysis`) — flags items the statistics say are weak: too easy, too hard, low discrimination, distractor under-pick. The threshold (minimum attempts before stats appear) is editable inline; the default is 30. Raise the threshold for low-volume courses, lower it for high-volume ones.

**AI usage** (`/admin/learn/ai-usage`) — Anthropic token spend per feature for the trailing 30 days. Tracks question-generation, lesson-takeaway, and course-description calls separately so you can see which features are pulling weight.

## Integrations — SCIM, outbound xAPI

**SCIM 2.0** (`/admin/learn/scim-credentials`) — inbound user/group provisioning from an enterprise IdP. Generate a bearer token, paste it into Okta / Entra ID / Workday / Ping / JumpCloud, and users + groups push in automatically. Group memberships map to mobieusLearn cohorts on the way through. See the [SCIM 2.0 IdP setup guide](/know/learn-scim-setup) for step-by-step setup.

**Outbound xAPI** (`/admin/learn/xapi-outbound`) — forward every xAPI statement to an external Learning Record Store. Configure endpoint + Basic auth, hit Test, save. Statements mirror in real time; the worker retries on transient failures.

## Audit log + Settings

**Audit log** (`/admin/learn/audit`) — every admin action that mutated learn state. Filter by actor, event type, or date range. Use this when investigating "who changed what when".

**Settings** (`/admin/learn/settings`) — the home for tenant-wide Learn configuration:

- **Open Badges issuer** card — shows whether the Ed25519 signing key is provisioned. If not, click "Provision issuer keypair" and the system generates one.
- **mobieusAI authoring** card — paste an Anthropic API key to enable AI-assisted course authoring. The key is stored on this tenant only. Use "Rotate or remove" to change it. (The community-wide AI control plane — master switch, spend caps, and the AI helpers outside authoring — lives at `/admin/ai`.)
- **Native xAPI LRS** card — informational only; every statement lives in the tenant's own database.
- **Item analysis threshold** card — links to the inline editor on the item-analysis page.

## Video lessons

Add a video straight into a lesson. In the course canvas, add an activity and set its kind to **Video**, save it, then upload the file on the activity's edit screen. Mobieus prepares the video for smooth playback that adapts to each viewer's connection and device, and the lesson plays it inline — no separate video host and no encoding settings to fiddle with.

- **Formats** — MP4, MOV, WebM, or MKV.
- **Length** — your plan sets the longest video you can upload: 30 minutes on Pro, 2 hours on Creator Plus, and no limit on Sovereign. A file over the limit is rejected with a clear message after it uploads.
- **Processing** — right after you upload, the video shows as processing for a few minutes while it is prepared, then flips to ready. Replace the file at any time from the same panel.
- **Completion** — set the activity's completion criteria to **Viewed**. Finishing the video (or the learner clicking Mark complete) completes the lesson, and learners resume right where they left off.

Course video is included on Pro, Creator Plus, and Sovereign.

## Common workflows

**Launch a course end-to-end**
1. Create a category if you need one.
2. New course under that category, draft state.
3. Add modules + lessons inside the course; populate activities (video, reading, assessment).
4. Build a cert template (or accept the default) and attach it to the course.
5. Optionally create a badge tied to course completion.
6. Submit course for review; reviewer approves; status flips to published.
7. Either sell it via mobieusCore (Products → New course), grant via cohort, or open enrollment to all members.

**Bring an organization's roster in via SCIM**
1. Settings → confirm Open Badges issuer is provisioned (needed for credential signing).
2. SCIM 2.0 page → New credential → Pick a name → Copy the bearer token (shown once).
3. In the IdP, point SCIM at `https://<your-tenant>.mobieus.io/scim/v2/` and paste the token.
4. Map IdP groups to mobieusLearn cohorts using the cohort-name suffix convention (see the [SCIM guide](/know/learn-scim-setup)).
5. Watch the IdP push the initial roster; subsequent changes flow on the IdP's SCIM cadence.

**Wire up an external LMS to launch into a mobieusLearn course**
1. Authoring → LTI 1.3 → copy your tool's JWKS URL + Login Initiation URL + Redirect URI.
2. In the external LMS, register Mobieus as a new LTI 1.3 tool with those URLs.
3. The external LMS gives you a Platform Issuer + Client ID + Deployment ID + Platform JWKS URL.
4. Back in mobieusLearn, paste those values into the New platform form.
5. Add a course as a launchable resource; the platform's instructors can now embed it.

## What's NOT in this guide

Per-learner experience (the `/learn/my` dashboard, course consumption, assessment-taking, the credential wallet) is covered in the [learner dashboard guide](/know/mobieuslearn-learner-guide). This guide is for admins.

## Related articles

- [Your learning dashboard](/know/mobieuslearn-learner-guide)
- [mobieusLearn SCIM 2.0 — IdP setup guide](/know/learn-scim-setup)
- [mobieusCore API — mobieusLearn](/know/api-learn)