Skip to content

Identifying learners

Learner memory remembers values for each learner, so SlideMind first needs to know who the learner is. This page explains where the learner’s identifier comes from, in which order SlideMind looks for it, what never identifies anyone, and how to choose an identifier that respects privacy. It is for course authors and the LMS administrators who launch their courses.

Learner memory works only for an identified learner: saving values, reusing them in later slides, and remembering conversations. Without an identifier, as the app puts it, “the chat works, the memory stays off.”

ActivityWithout an identified learner
Q&A and ChatThe slide answers normally. Nothing is saved for later slides. In your instructions, a memory placeholder shows its fallback text, or disappears.
Capture (authoring tool code)Nothing is saved. The code stops with the error “SlideMind learner identifier is missing”, which the browser’s developer console usually shows.
Embedded capture (HTML widget)Nothing is saved, and the widget answers with the no_learner_uid error.

See How learner memory works and Using values in prompts.

The integration code looks for the identifier in this order and keeps the first one it finds:

OrderSourceWhat SlideMind reads
1sm_user parameterThe identifier written in the address, for example ?sm_user=learner-4821.
2SCORM 2004cmi.learner_id, from your LMS.
3SCORM 1.2cmi.core.student_id, from your LMS.
4Articulate SCORM driverThe learner ID exposed by courses published from Storyline and Rise 360.
5xAPIThe actor launch parameter: its e-mail address (without mailto:) or its account name. The code also reads it from the course page above it, for example around a Rise 360 Code block.
6cmi5The actor your LMS returns through the fetch launch parameter (an https address only).
7Address parametersuser_id, then learner_id, then student_id.

For SCORM, the code searches the windows around the course and the window that opened it, so courses that the LMS launches in a pop-up window work too.

Where the code runs decides which sources it can reach.

DestinationWhere the learner is detectedSources available
Authoring tool interface: Storyline (JavaScript), Captivate, Lectora, dominKnow | ONE, iSpring SuiteInside the published courseAll seven
Rise 360 (Code block) and Storyline (Web Object)Inside the published course, by the generated script, which then passes the identifier to the widget as sm_userThe LMS connection of the published course: SCORM 2004, SCORM 1.2 and the Articulate SCORM driver, and the xAPI actor of the course page
HTML widget (iframe)Inside the widget, on SlideMind’s addressOnly its own address: sm_user, actor, user_id, learner_id, student_id

An HTML widget runs on SlideMind’s address, not your site’s, and the browser does not let it read the LMS session of the page around it. To identify learners there, add sm_user to the iframe address. See HTML widget (iframe).

The address parameters (sm_user, actor, fetch, user_id, learner_id, student_id) are read from the address of the page where the code runs. For a Rise 360 Code block or a Storyline Web Object, that is the block or the Web Object itself, not the address your LMS used to launch the course.

The app is explicit: “Share links, Review 360 and authoring-tool previews never identify anyone: the chat works, the memory stays off.” In practice:

  • Authoring-tool previews (Storyline, Rise 360, Captivate and the others) run outside an LMS.
  • Review 360 and share links let reviewers see the course, but no LMS tells SlideMind who they are.
  • A course opened outside an LMS, for example from a web server, has no learner, unless the address where the integration code runs carries sm_user or one of the address parameters above.
  • SlideMind’s own tests. Try it “never saves anything”, and the widget preview in the slide editor never detects a learner.

To test learner memory, launch the published package as a test learner in the SCORM preview, from your LMS, or from a SCORM test service such as SCORM Cloud. See Test before going live.

When the code cannot read an LMS, as with an HTML widget on a website or an LMS page, add sm_user to the address:

<iframe
src="https://api.slidemind.app/widget/abc123?mode=qa&sm_user=learner-4821"
width="100%" height="480" frameborder="0"
title="Coaching feedback"
allow="clipboard-write"></iframe>
  • The value must be the identifier of the person viewing the page. Use what your LMS or site offers to insert the current user’s ID, or build the address on your server.
  • Never type a fixed value for everyone: all learners would then share a single memory.
  • URL-encode the value (for example, @ becomes %40). It can be up to 255 characters long.

SlideMind stores the identifier exactly as it receives it: an e-mail address, a username or an LMS number. It does not check who the identifier belongs to, and it does not change it.

  • Exact match. Learner@example.com and learner@example.com are two different learners for SlideMind.
  • Exact search. In Memory › Learner data, the search field needs the complete identifier. As the app says: “Paste the complete identifier. Encrypted learner data only supports exact search.”
  • Same source, same learner. Memory follows the learner from one course to the next only if every course reports the same identifier. If one course reports an e-mail address through xAPI and another an LMS number through SCORM, SlideMind sees two different learners.
  • One memory per workspace. The same identifier in two workspaces has two separate memories.

Privacy: prefer an LMS ID to an e-mail address

Section titled “Privacy: prefer an LMS ID to an e-mail address”

When your LMS or your integration lets you choose, prefer an internal LMS ID (a number or an opaque code) to an e-mail address:

  • SlideMind then holds less personal data about your learners.
  • An sm_user value is visible in the page’s address and source.
  • With xAPI, an actor described by an account name gives SlideMind that name instead of the learner’s e-mail address.

To find a learner later in Learner data, for example to answer an access or deletion request, you need that same identifier. Make sure you can look it up in your LMS. See Learner data and Data, AI providers and your responsibilities.

  • In an HTML widget, the sm:ready message tells the page around the widget whether a learner was detected (learnerDetected). See Advanced: messages for developers.
  • In authoring tool code, a Capture slide that finds no learner stops with the error “SlideMind learner identifier is missing”. Look for it in the browser’s developer console.