Glossary¶
Terms used throughout PulseLMS and this documentation, in alphabetical order.
Act-as (impersonation)¶
An admin capability to temporarily view PulseLMS as another user for troubleshooting, seeing exactly what that person sees. Actions taken while acting-as are attributed to the admin in the audit log.
Achievements¶
The gamification layer: points, a level, a learning streak, and badges earned as you complete training. Lives under Achievements in the sidebar.
API key¶
A per-organization secret (pls_…) used to authenticate the partner API.
Created under Settings → API keys, shown once, and carrying one or more
scopes (read, enroll:write). See the API guide.
Assignment¶
A course or program given to a person, team, or role, optionally with a due date. Assignments drive Dashboard reminders and can recur (for example, annual compliance retraining).
Audit log¶
An org-admin record of significant administrative actions: role changes, publishes, assignments, branding and flag changes, exports, and certificate revocations. Each carries the actor and a timestamp.
Blocking check¶
A quiz or knowledge check that must be passed before the learner can proceed to the next lesson or complete the course. Contrast with a non-blocking knowledge check.
Catalog¶
The browsable list of published courses available to a learner, with ratings, reviews, tags, difficulty, and duration. May include self-enrollment where enabled.
Certificate¶
A verifiable proof of completion issued to a learner, identified by a serial anyone can check publicly. Certificates may have an expiry and a recertification cycle.
Edition¶
Which packaged version of PulseLMS an organization runs, Enterprise or Community, determining the available feature set and gating.
E-signature (attestation)¶
A compliance step on mandatory courses where the learner affirms they completed and understood the material. The signature is recorded with a timestamp as part of the completion record.
Knowledge check¶
A lightweight, usually non-blocking quiz used to reinforce learning within a lesson. Contrast with a blocking check.
Manager¶
A team-scoped role: everything an admin can do, but limited to the manager's own team: view progress, assign training, run team reports, and nudge. See teams & managers.
No-skip (video)¶
A player setting that prevents a learner from jumping past unwatched portions of a video. Pausing, rewinding, captions, chapters, and speed control still work.
Nudge¶
A one-click prompt from a manager or instructor to a learner who is behind,
delivered as a nudge notification.
Notification bell¶
The top-bar icon listing your in-app notifications with an unread count. Many types are also sent by branded email. See notifications & events.
Organization (tenant)¶
A single customer's isolated workspace: its own people, courses, branding, and data. PulseLMS is multi-tenant: you only ever see your own organization. An organization has an alias used for its public catalog URL. A platform admin can change it; every alias an organization has held goes on resolving, so old links keep working.
Partner API¶
The API-key-authenticated REST surface at /api/public/v1 for external
integrations. See the API guide.
Program¶
An ordered learning path of courses that unlock sequentially: finish one (and pass any required check) before the next opens. May include prerequisites and recurring assignment.
Publish notes¶
A short, learner-facing changelog an author attaches when publishing a new
version of a course, so enrolled learners see what changed (delivered via the
course_updated notification).
Publishing¶
Snapshotting a course into a new immutable version that learners see. Editing a draft doesn't affect learners until it's published.
Recertification (recert)¶
A cycle that requires a learner to retake a course to renew an expiring
certification, common for annual compliance. Prompted by the recert_due
notification.
Reports v2¶
The current reporting surface: learner transcripts, team/department rollups, quiz item-analysis, time-range filters, and exported or scheduled reports.
Role¶
One of six access levels (learner, instructor, author, manager, org admin, platform admin) determining what a person can see and do. See the role matrix.
Scope (API)¶
A permission attached to an API key limiting what it can do: read
(read-only) or enroll:write (also enroll users).
SSO (single sign-on)¶
Authentication delegated to your organization's identity provider; PulseLMS never stores a password. Enterprise customers can federate their own IdP via SAML/OIDC. See getting started.
Team¶
A group of members a manager oversees. Training can be assigned to a whole team, and reports can be rolled up by team. See teams & managers.
Transcript¶
A learner-centric record of one person's activity across all courses: their completions, scores, and certificates, available in Reports v2.
Webhook¶
An HTTPS endpoint PulseLMS calls when an event occurs (enrollment, completion, certificate, publish, program completion). Deliveries are signed with HMAC-SHA256. See notifications & events.
White-label (branding)¶
Customizing the workspace with your organization's logo, colors, and name so PulseLMS reflects your brand. Configured under settings & branding.