Skip to content

How learner memory works

Learner memory lets your slides remember something about each learner, such as a first name, a profession, a goal or a summary of a role-play, and reuse it in any later slide of the workspace. This page explains how memory works. Read it before you set up your first memory value.

  1. Your authoring tool
  2. Silent capture
  3. Learner memory
  4. Any other slide

For example, an intro screen in Storyline asks for the learner’s profession. A slide saves it to memory under the key profession. Every later slide can then insert {{memory.profession}} in its instructions, so the AI adapts its feedback to that profession.

Video tutorial, Ep. 4: Learner memory across courses. Two memory variables captured in one Storyline course and reused in the feedback of another, tested in SCORM preview. Steps and texts to copy on SlideMind Academy ↗
ConceptWhat it meansExample
Identified learnerA learner that SlideMind can recognize from one session to the next. Memory exists only for identified learners.learner@example.com or an LMS identifier
Memory keyThe name under which a value is stored. Keys use letters, digits and underscores, and cannot start with a digit.profession
ValueThe text that is stored for one learner under one key.Nurse
ScopeWhere the value can be read back: the whole workspace, one course, one module or one slide.Global

A slide can save values in three ways: a Capture slide, exchange memory on a Q&A or Chat slide, and capture during the AI call. See Saving values. The Memory Hub can also generate code that saves values from a screen that has no SlideMind slide. To read values back, see Using values in prompts.

In practice, a learner is identified in these cases:

  • the course is launched from an LMS (SCORM, xAPI or cmi5);
  • the embed URL carries an sm_user parameter.

The exact sources, and their order, depend on the destination: see Identifying learners.

Share links, Review 360 and authoring-tool previews never identify anyone. In those cases, slides still answer learners normally, but nothing is saved to memory and nothing is read from it.

Each value is stored at one scope. The scope decides which slides can read it back.

ScopeOne value per learner…Use it for
Globalshared across all courses of the workspaceA first name, a profession, a preference. Choose this if in doubt.
Courseper course: only slides of the same course read itA choice the learner made earlier in this course
Moduleper module: only slides of the same module read itA score or an answer that only matters inside one module
Slideper slide: only this slide reads itA value that one slide keeps for itself

The Course and Module scopes need a slide that belongs to a course or a module. When a slide is not attached, the slide editor shows these scopes with “attach the slide first”. See Courses and modules.

The same key can exist at several scopes, for example a Global level and a Course level. When a slide reads {{memory.level}}, it uses the most specific value it can see:

  1. Slide: a value saved for this slide.
  2. Module: a value saved for this slide’s module.
  3. Course: a value saved for this slide’s course.
  4. Global: a value shared by the whole workspace.

A slide only sees its own slide, module and course values, plus Global values. A Course value saved in another course is never read.

You can also force a scope, for example {{memory.global.level}}. See Using values in prompts.

Memory holds the latest state, never several versions. Each save under the same key, at the same scope and for the same learner, overwrites the previous value. For example, a Chat slide that keeps the conversation rewrites that value after each AI reply.

If two settings of the same slide write the same key at the same scope, the slide editor shows a warning. Sharing a key can be intentional: later writes overwrite earlier ones.

Values stay in memory until one of these happens:

  • Retention period. In Settings › Data & privacy, the Memory retention (days) field sets how long values are kept. The default, 0, keeps learner memory indefinitely. With another number, a value that has not been updated for that many days is deleted automatically.
  • Manual deletion. A workspace owner deletes a value or purges a learner in Learner data.
  • Workspace deletion. When a deleted workspace’s grace period ends, its learner memory is permanently deleted. See Delete or restore a workspace.

Only the workspace owner can change the retention period. Editors see it read-only.

TaskOwnerEditorViewer
Set up memory on a slideYesYesNo
Define, edit or delete variables in the Memory HubYesNoNo
Generate Memory Hub codeYesYesNo
See the list of learners with stored valuesYesYesNo
Open, correct, export or purge a learner’s valuesYesNoNo

Viewers do not have access to the Memory pages. See Members and roles.