$id:UUID!,

$title:String,

$status:String,

$sku:String,

$seatsLimit:Int,

$priceInCents:Int,

$customFields:[CustomFieldInput!],

$courseStartDate:Date,

$enrollmentStartDate:Date,

$enrollmentEndDate:Date,

$meetings:[MeetingFields!]

){UpdateInPersonEvent(

id:$id,

title:$title,

status:$status,

sku:$sku,

seatsLimit:$seatsLimit,

priceInCents:$priceInCents,

customFields:$customFields,

courseStartDate:$courseStartDate,

enrollmentStartDate:$enrollmentStartDate,

enrollmentEndDate:$enrollmentEndDate,

meetings:$meetings

){

id,

createdAt,

updatedAt,

slug,

status,

title,

seatsLimit,

courseStartDate,

courseEndDate,

enrollmentStartDate,

enrollmentEndDate,

sku,

meetings{

id,

title,

attendeeInfo,

startDate,

endDate

}

}}

Watch the 45-minute demo walkthrough: View Recording →

Questions? Reply below or email success@thoughtindustries.com.

Join us monthly for our What’s New? Webinar to understand the impact of our product releases and latest innovations. Each session delivers a dynamic, visual walk-through of our most impactful enhancements including what’s new and what you should do next.

We’ll take a tour of the new capabilities and how they work, where they shine, and how to put them to work quickly. This is your shortcut to staying current in the platform, so you can turn TI updates into your business momentum!

🚀 Join us live on the first Wednesday of each month at 11am EST for an overview of our most impactful releases from the past month.

Note: While we won’t be providing live support or troubleshooting during this time, we’re always happy to point you in the right direction or connect you with resources that can help.

• API Basics & Core Terms

• Understanding API Requests

• Why Use APIs (and risks to know before you start)

• Your First API Recipe: Export Your Course Data

• Your Second API Recipe: Reset & Revoke Course Access

  
  
  By the end, you won't just understand APIs - you'll have actually used them.
  Open to everyone. No experience required.
  
  👉 Check it out here

Learn how the Institute of Management Accountants transformed their learning operations from a highly manual, time-intensive process into a scalable machine that publishes up to 50 courses per day.

In this virtual roundtable, Emily Masterson (Strategic Design Lead) and Eric Regnell (Curriculum Innovation Specialist) from IMA share the strategic framework and practical systems that enable their team to respond to market shifts within days—not months.

Key Takeaways

• Start with a Clear Plan: IMA built a framework that defines what accountants need to know—no more guessing what to teach

• Build Small, Reuse Often: Break courses into bite-sized pieces that can be mixed and matched into different learning paths

• Move Fast: Launch courses in weeks, not months. Some courses are built in just an afternoon

• Use the Right Tools: Stick with tools like Articulate and templates so your team stays consistent and doesn't reinvent the wheel

• Automate the Repetitive Work: Use APIs to publish dozens of courses at once instead of uploading them one by one

• Organize Your Content: Managing 500+ courses is messy—hear how IMA keeps everything organized and findable

Who Should Watch

• Learning leaders managing growing course catalogs

• Instructional designers wanting to move faster without losing quality

• Curriculum teams struggling with content organization and reuse

• Organizations considering micro-credentials or atomic learning architecture

• Anyone who's asked: "How do we scale course development with a lean team?"

What to Expect

Real, practical wisdom from IMA's years of platform experience—including what's working brilliantly, lessons learned the hard way, and the ongoing challenges they're solving right now. This isn't a polished case study. It's a working conversation with peers who've done the work.

Once a learner completes all content in a Featured Content widget on their dashboard, that widget becomes a wall of checkmarks that adds visual clutter without adding value. This play gives you a lightweight script that automatically hides any Featured Content widget where all items are completed — keeping the dashboard clean and focused on what still needs the learner's attention. Content remains assigned and tracked in reporting; it's simply hidden from the dashboard view.

Requirement Overview

If any of these requirements fit your end goal, this may be the play for you.

• Requirement 1: You use Featured Content widgets on the learner dashboard to highlight specific content (e.g., onboarding courses, recommended training, promoted content).

Requirement 2: You want those widgets to disappear automatically once the learner has completed everything in them, so the dashboard stays focused on active or upcoming work.

Functional Areas to be Used

• Custom Scripts (Site → Site Builder → Pages → Dashboard → Custom Scripts)

• Dashboard Layout

• Featured Content Widgets (Tiles, Carousel, or Standard)
  
  

  

Core Functionality Configurations

How the Script Works

Description: The script runs on the learner dashboard after the page loads. It looks at every Featured Content widget on the page, counts the total number of content items in each widget, and compares that to the number of completed items. If every item in a widget is completed, the widget is hidden. This is a visual-only hide — the content remains assigned to the learner, remains visible in the Learner Access Widget, and continues to appear in reporting.

What the script is actually doing:

1. Wait 1.5 seconds after page load to allow all widgets to render.

2. Find all elements with the class .widget--featured-content (this is the class TI uses for Featured Content widgets).

3. For each widget, count the total content items (.catalog-grid-item) and the completed items (.catalog-grid-item__completed).

4. If total equals completed and total is greater than zero, hide the widget.
   
   

   ---

   
   What to Customize for Your Instance

5. The delay before running (1500ms). If your dashboard loads slowly and widgets haven't fully rendered by the time the script runs, increase this value. If your dashboard loads quickly, you can decrease it for a snappier experience:
   

}, 1500);

The widget selector. The script targets .widget--featured-content, which covers Featured Content Tiles, Featured Content Carousel, and standard Featured Content widgets. If you want to apply this logic to a different widget type, change the selector:

var widgets = document.querySelectorAll('.widget--featured-content');

The completion indicator. The script checks for the class .catalog-grid-item__completed to identify completed items. If TI changes this class name in a future update, you'll need to update this selector:

var completed = widget.querySelectorAll('.catalog-grid-item__completed').length;

The content item selector. The script uses .catalog-grid-item to count all content items in a widget. Same consideration as above — if TI changes this class, update accordingly:

var total = widget.querySelectorAll('.catalog-grid-item').length;

The Script

Install the entire script below with your customizations into the Custom Scripts area of your Dashboard layout (Site → Site Builder → Pages → Dashboard).

Installation

Configuration

1. Navigate to Site → Site Builder → Pages.

2. Open the Dashboard layout.

3. Locate the Custom Scripts area.

4. Paste the entire script below (including the <script> tags) into the Custom Scripts field.

5. Save the layout.

6. Test by logging in as a learner who has completed all content in at least one Featured Content widget.

<script>
(function () {

  // ──────────────────────────────────────────────
  // AUTO-HIDE COMPLETED FEATURED CONTENT WIDGETS
  // Hides any Featured Content widget where all
  // content items have been completed by the learner.
  // Visual only — does not affect enrollment,
  // reporting, or the Learner Access Widget.
  // ──────────────────────────────────────────────

  // Only run on the dashboard
  if (window.location.pathname !== '/learn/dashboard') return;

  function hideCompletedWidgets() {
    var widgets = document.querySelectorAll('.widget--featured-content');
    widgets.forEach(function (widget) {
      var total = widget.querySelectorAll('.catalog-grid-item').length;
      var completed = widget.querySelectorAll('.catalog-grid-item__completed').length;
      if (total > 0 && completed === total) {
        widget.style.display = 'none';
      }
    });
  }

  // Wait for widgets to render before checking
  setTimeout(hideCompletedWidgets, 1500);

  // ──────────────────────────────────────────────
  // SPA NAVIGATION — re-run when learner returns
  // to the dashboard via in-app navigation
  // ──────────────────────────────────────────────

  function checkIfDashboard() {
    if (window.location.pathname === '/learn/dashboard') {
      setTimeout(hideCompletedWidgets, 1500);
    }
  }

  window.addEventListener('popstate', checkIfDashboard);

  var originalPushState = history.pushState;
  history.pushState = function () {
    originalPushState.apply(this, arguments);
    setTimeout(checkIfDashboard, 100);
  };

  var originalReplaceState = history.replaceState;
  history.replaceState = function () {
    originalReplaceState.apply(this, arguments);
    setTimeout(checkIfDashboard, 100);
  };

})();
</script>

Testing Checklist

• A Featured Content widget where all items are completed is hidden on the dashboard.

• A Featured Content widget where some but not all items are completed remains visible.

• A Featured Content widget with no completed items remains visible.

• An empty Featured Content widget (zero items) remains visible (the script only hides when total > 0 and total equals completed).

• The Learner Access Widget still shows all assigned content, including completed items — this script only affects Featured Content widgets.

• Navigate away from the dashboard and back — the hide logic re-runs and widgets are correctly hidden again.

• Content that was in a hidden widget still appears in reporting and in the learner's content actions log.

Risk and Mitigation Strategy

• Any CSS or JavaScript added via custom scripts may not be supported by the Thought Industries Technical Support team. This is a custom implementation — document it internally.

  • You can use a tool like Visual Studio to store your code internally.

• This is a visual-only hide (display: none). The content is still assigned to the learner, still tracked in reporting, and still visible in the Learner Access Widget. No enrollment or completion data is affected.

• The script depends on TI's CSS class names (.widget--featured-content, .catalog-grid-item, .catalog-grid-item__completed). If TI changes these class names in a platform update, the script will stop working. It will fail silently — widgets will simply remain visible rather than being hidden. Test after platform updates.

• If new content is added to a previously hidden widget (e.g., you add a new course to a tag that powers a Featured Content widget), the widget will remain hidden for learners who had previously completed all items — until the next full page reload or dashboard navigation, at which point the script recalculates and will show the widget again (since total will now be greater than completed).

• The script overrides history.pushState and history.replaceState for SPA navigation handling. If you have other custom scripts on your instance that do the same (including the Welcome Card script from the companion configuration play), they can coexist — each one wraps the previous override. However, test them together to ensure no conflicts.

• If using both this script and the Welcome Card script (link to welcome card config play), you can paste them both into the Custom Scripts area sequentially. They are designed as independent modules and do not share variables or state. The Welcome Card script does not include the hide-completed-widgets logic, so both scripts are needed if you want both features.

• Dashboard path: The script checks for /learn/dashboard. If your instance uses a different dashboard URL, update this path in both locations in the script.

Want your learners to feel like the platform knows them the moment they land on their dashboard? This play walks you through a custom script that adds a branded welcome card to the top of the learner dashboard — greeting them by name with a time-appropriate message, optionally displaying contextual information from their profile (like their product or team), showing them where they left off with a direct link to their last course, and providing a "Continue Learning" button that scrolls them to their assigned content. The card is fully customizable to match your brand.

Requirement Overview

If any of these requirements fit your end goal, this may be the play for you.

• Requirement 1: You want a personalized greeting on the dashboard that addresses the learner by first name and changes based on time of day (Good morning / Good afternoon / Good evening).

• Requirement 2: You want to display contextual information from the learner's profile — such as their product, team, or organization — pulled from a learner reference field.

• Requirement 3: You want a "Pick up where you left off" link that remembers the last course a learner visited and provides a direct link back to it.

Requirement 4: You want a "Continue Learning" button that scrolls the learner down to their assigned content on the dashboard.

Functional Areas to be Used

• Custom Scripts (Site → Site Builder → Pages → Dashboard → Custom Scripts)

• Learner Reference Fields (for personalized data like product or role)

• Dashboard Layout - this can be added to the global layout or any customized panorama layout

• CSS Styling

Core Functionality Configurations

Understanding the Script & What It Does

Description: This script is a single block of JavaScript that runs on the learner dashboard. It does four things:

1. Personalized Welcome Card — A styled card at the top of the dashboard with a time-based greeting, the learner's first name, an optional product/context line pulled from a reference field, a subtitle message, and a "Continue Learning" button.
   
   

2. Last Course Tracking — Tracks the last course the learner visited using the browser's localStorage (scoped per learner) and displays a "Pick up where you left off" link inside the welcome card.
   
   

3. Continue Learning Button — A button on the welcome card that smooth-scrolls the learner down to the Learner Access Widget (their assigned content section) on the dashboard.
   
   

Navigation Handling — The script intercepts browser history events to ensure tracking and display logic work correctly as learners navigate between the dashboard and course pages without full page reloads.

1. The Personalized Welcome Card

Description: The core visual component. Injects a styled card directly below the dashboard header that greets the learner by name with a time-appropriate message. Optionally displays a value from a learner reference field (e.g., their product, team, or company).

How it works: The script reads the learner's first name and a reference field value from the TI platform's window.CONF.preload.currentUser object — this is data that TI makes available on every page for the logged-in user. It determines the time of day and selects "Good morning," "Good afternoon," or "Good evening." It then builds an HTML card element and injects it into the dashboard DOM directly after the dashboard header.

What to customize for your instance:

The eyebrow text — the small label above the greeting. In the script it reads "FlowStack Academy." Find this line and change it to your academy or program name:

'<p class="wc-eyebrow">Your Academy Name</p>'

The reference field used for the product/context line. The script reads from ref4:

product = window.CONF.preload.currentUser.currentUser.ref4 || '';

Change ref4 to whichever reference field holds the value you want to display (e.g., ref1, ref2, ref3). If you don't want to display a reference field value at all, you can remove this line and the corresponding HTML block:

product ? '<p class="wc-product">' + product + '</p>' : '',

The subtitle text — the line below the greeting:

'<p class="wc-sub">Great to have you here. Keep building momentum — every lesson gets you one step closer to your goals.</p>'

The CSS styling — The script injects its own CSS for the welcome card. Key values you'll likely want to customize to match your brand:

To match your brand colors, do a find-and-replace on the primary blue values (#2b6ff5, #185fa5, #1a5de0, #2b7de9, #5b9cf6) with your brand's primary and secondary colors.

2. Last Course Tracking ("Pick Up Where You Left Off")

Description: Tracks the last course the learner visited and displays a "Pick up where you left off" link inside the welcome card with the course title and a direct link back to it.

How it works: The script intercepts SPA navigation events across the entire platform. Whenever the learner navigates to a URL containing /learn/course/ or /courses/, the script waits 800ms (to let the page title update), captures the course title from document.title, and saves it to localStorage with a key scoped to the learner's user ID.

When the learner returns to the dashboard, the script reads from localStorage and displays the "Pick up where you left off" section inside the welcome card.

What to customize for your instance:

The localStorage key prefix. The script uses fs_last_course_. Change this to match your brand:

var storageKey = 'fs_last_course_' + userId;

The URL patterns that trigger tracking. If your instance uses different URL patterns for content, update this condition:

if (path.indexOf('/learn/course/') !== -1 || path.indexOf('/courses/') !== -1) {

The delay before capturing the title (800ms). If your instance loads slowly, increase this value:

setTimeout(function () { ... }, 800);

Risk and Mitigation Strategy:

• This feature uses localStorage, which is browser-specific and can be cleared by the learner. It does not persist across browsers or devices.

• The script parses the course title from document.title by splitting on - and taking the first segment. If your page titles are formatted differently, the displayed title may be incorrect. Test with your actual content.

3. Continue Learning Button

Description: A button on the welcome card that smooth-scrolls the learner down to their assigned content section on the dashboard (the Learner Access Widget).

What to customize for your instance:

The target element for scrolling. If your primary content section uses a different widget, change the CSS selector:

var target = document.querySelector('.dashboard-access__header');

The fallback scroll distance (500 pixels). Adjust based on your dashboard layout:

window.scrollBy({ top: 500, behavior: 'smooth' });

The button text:

'Continue Learning ',

4. Navigation Handling

Description: The script intercepts history.pushState, history.replaceState, and popstate events to ensure the last-course tracking works as learners navigate between pages, and to re-inject the welcome card when learners return to the dashboard.

What to customize for your instance:

The dashboard path. The script checks for /learn/dashboard. If your instance uses a different dashboard URL, update these checks:

if (window.location.pathname !== '/learn/dashboard') {

var onDashboard = window.location.pathname === '/learn/dashboard';

The Script

Make any customizations you need from above to the script below and then put the entire script into the Custom Scripts area of your Dashboard layout (Site → Site Builder → Pages → Dashboard).

Installation

Configuration

1. Navigate to Site → Site Builder → Pages.

2. Open the Dashboard layout.

3. Locate the Custom Scripts area.

4. Put the entire script below with your customizations (including the <script> tags) into the Custom Scripts field.

5. Save the layout.

6. Test by logging in as a learner and navigating to the dashboard.

<script>
(function () {

  // ──────────────────────────────────────────────
  // LAST COURSE TRACKING — scoped per learner
  // ──────────────────────────────────────────────
  var userId = '';
  try {
    userId = window.CONF.preload.currentUser.currentUser.id || '';
  } catch (e) {}
  var storageKey = 'fs_last_course_' + userId;

  function trackCourseIfOnCoursePage() {
    var path = window.location.pathname;
    if (path.indexOf('/learn/course/') !== -1 || path.indexOf('/courses/') !== -1) {
      setTimeout(function () {
        try {
          var title = document.title.split(' - ')[0].trim();
          if (title && storageKey) {
            localStorage.setItem(storageKey, JSON.stringify({
              title: title,
              url: path,
              time: Date.now()
            }));
          }
        } catch (e) {}
      }, 800);
    }
  }

  // Run on initial load in case learner lands directly on a course page
  trackCourseIfOnCoursePage();

  // ──────────────────────────────────────────────
  // NON-DASHBOARD PAGES — track courses only, exit early
  // ──────────────────────────────────────────────
  if (window.location.pathname !== '/learn/dashboard') {
    var _push = history.pushState;
    history.pushState = function () {
      _push.apply(this, arguments);
      setTimeout(trackCourseIfOnCoursePage, 100);
    };
    var _replace = history.replaceState;
    history.replaceState = function () {
      _replace.apply(this, arguments);
      setTimeout(trackCourseIfOnCoursePage, 100);
    };
    window.addEventListener('popstate', trackCourseIfOnCoursePage);
    return;
  }

  // ──────────────────────────────────────────────
  // DASHBOARD — personalized welcome card
  // ──────────────────────────────────────────────

  // Read learner data
  var firstName = '';
  var product = '';
  try {
    firstName = window.CONF.preload.currentUser.currentUser.firstName || '';
    firstName = firstName.charAt(0).toUpperCase() + firstName.slice(1);
    product = window.CONF.preload.currentUser.currentUser.ref4 || '';
  } catch (e) {}
  if (!firstName) firstName = 'there';

  // Time-based greeting
  var hour = new Date().getHours();
  var greeting = hour < 12 ? 'Good morning' : hour < 17 ? 'Good afternoon' : 'Good evening';

  // State
  var sectionCreating = false;

  // ──────────────────────────────────────────────
  // CSS — customize colors to match your brand
  // ──────────────────────────────────────────────
  var style = document.createElement('style');
  style.textContent = [
    '#ti-welcome-card *{box-sizing:border-box;margin:0;padding:0}',
    '#ti-welcome-card{background:linear-gradient(135deg,#e8edf7 0%,#eef1fa 60%,#e6f1fb 100%);border-radius:16px;padding:36px 40px;margin:0 0 28px;display:flex;align-items:center;position:relative;overflow:hidden;border:1px solid rgba(24,95,165,.15);font-family:inherit}',
    '#ti-welcome-card .wc-geo{position:absolute;right:-20px;top:0;bottom:0;width:260px;pointer-events:none;z-index:1}',
    '#ti-welcome-card .wc-left{flex:1;position:relative;z-index:2;max-width:520px}',
    '#ti-welcome-card .wc-eyebrow{font-size:11px;font-weight:700;text-transform:uppercase;letter-spacing:.1em;color:#185fa5;margin-bottom:6px;display:flex;align-items:center;gap:8px}',
    '#ti-welcome-card .wc-eyebrow::before{content:"";display:inline-block;width:20px;height:2px;background:#2b7de9;border-radius:2px}',
    '#ti-welcome-card .wc-product{font-size:12px;font-weight:600;color:#2b6ff5;margin-bottom:8px;letter-spacing:.02em;display:inline-flex;align-items:center;gap:6px}',
    '#ti-welcome-card .wc-product::before{content:"";display:inline-block;width:6px;height:6px;border-radius:50%;background:#2b6ff5}',
    '#ti-welcome-card .wc-headline{font-size:30px;font-weight:800;color:#1a1d2e;line-height:1.2;margin-bottom:10px;letter-spacing:-.02em}',
    '#ti-welcome-card .wc-headline span{color:#2b6ff5}',
    '#ti-welcome-card .wc-sub{font-size:14px;color:#4a5568;line-height:1.6;margin-bottom:24px;max-width:440px}',
    '#ti-welcome-card .wc-actions{display:flex;align-items:center;gap:12px;flex-wrap:wrap}',
    '#ti-welcome-card .wc-btn{display:inline-flex;align-items:center;gap:8px;background:#2b6ff5;color:#fff;font-size:13px;font-weight:700;padding:11px 22px;border-radius:8px;border:none;cursor:pointer;letter-spacing:.01em;transition:background .18s,transform .15s;text-decoration:none}',
    '#ti-welcome-card .wc-btn:hover{background:#1a5de0;transform:translateY(-1px)}',
    '#ti-welcome-card .wc-btn svg{transition:transform .18s}',
    '#ti-welcome-card .wc-btn:hover svg{transform:translateX(3px)}',
    '#ti-last-accessed{margin-top:20px;padding-top:16px;border-top:1px solid rgba(24,95,165,.15)}',
    '#ti-last-accessed .wc-last-label{font-size:11px;font-weight:700;text-transform:uppercase;letter-spacing:.08em;color:#185fa5;margin-bottom:6px}',
    '#ti-last-accessed .wc-last-link{font-size:14px;font-weight:600;color:#1a1d2e;text-decoration:none;display:inline-flex;align-items:center;gap:6px;transition:color .15s}',
    '#ti-last-accessed .wc-last-link:hover{color:#2b6ff5}',
    '@media(max-width:600px){#ti-welcome-card{flex-direction:column;align-items:flex-start;padding:24px 20px}#ti-welcome-card .wc-headline{font-size:22px}#ti-welcome-card .wc-geo{display:none}}'
  ].join('');
  document.head.appendChild(style);

  // ──────────────────────────────────────────────
  // GEOMETRIC SVG ACCENT — decorative shape on right side of card
  // ──────────────────────────────────────────────
  var geoSvg = [
    '<svg class="wc-geo" viewBox="0 0 260 200" preserveAspectRatio="xMidYMid slice" xmlns="http://www.w3.org/2000/svg">',
      '<polygon points="260,0 130,0 260,110" fill="#2b6ff5" opacity="0.12"/>',
      '<polygon points="260,200 100,200 260,80" fill="#185fa5" opacity="0.10"/>',
      '<polygon points="260,60 160,0 260,0" fill="#2b6ff5" opacity="0.18"/>',
      '<polygon points="260,140 150,200 260,200" fill="#185fa5" opacity="0.16"/>',
      '<polygon points="220,200 260,140 260,200" fill="#5b9cf6" opacity="0.20"/>',
      '<polygon points="190,0 260,0 260,70" fill="#5b9cf6" opacity="0.14"/>',
    '</svg>'
  ].join('');

  // ──────────────────────────────────────────────
  // WELCOME CARD HTML — customize eyebrow, subtitle, button text
  // ──────────────────────────────────────────────
  var card = document.createElement('div');
  card.id = 'ti-welcome-card';
  card.innerHTML = [
    geoSvg,
    '<div class="wc-left">',
      '<p class="wc-eyebrow">FlowStack Academy</p>',
      product ? '<p class="wc-product">' + product + '</p>' : '',
      '<h2 class="wc-headline">' + greeting + ', <span>' + firstName + '</span>!</h2>',
      '<p class="wc-sub">Great to have you here. Keep building momentum — every lesson gets you one step closer to your goals.</p>',
      '<div class="wc-actions">',
        '<button class="wc-btn" onclick="tiScrollToLearning()">',
          'Continue Learning ',
          '<svg width="14" height="14" viewBox="0 0 14 14" fill="none">',
            '<path d="M2 7h10M8 3l4 4-4 4" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round"/>',
          '</svg>',
        '</button>',
      '</div>',
    '</div>'
  ].join('');

  // ──────────────────────────────────────────────
  // PICK UP WHERE YOU LEFT OFF — reads from localStorage
  // ──────────────────────────────────────────────
  function updateSection(course) {
    var courseUrl = course.url;
    var existingLink = document.querySelector('#ti-last-accessed .wc-last-link');
    if (existingLink) {
      existingLink.href = courseUrl;
      var lastNode = existingLink.lastChild;
      if (lastNode) lastNode.textContent = course.title;
      return;
    }
    if (sectionCreating) return;
    sectionCreating = true;
    var wcLeft = document.querySelector('#ti-welcome-card .wc-left');
    if (!wcLeft) {
      sectionCreating = false;
      setTimeout(function () { updateSection(course); }, 200);
      return;
    }
    var lastAccessed = document.createElement('div');
    lastAccessed.id = 'ti-last-accessed';
    lastAccessed.innerHTML = [
      '<p class="wc-last-label">Pick up where you left off</p>',
      '<a href="' + courseUrl + '" class="wc-last-link">',
        '<svg width="14" height="14" viewBox="0 0 14 14" fill="none">',
          '<circle cx="7" cy="7" r="6" stroke="#2b6ff5" stroke-width="1.5"/>',
          '<path d="M5.5 4.5l4 2.5-4 2.5V4.5z" fill="#2b6ff5"/>',
        '</svg>',
        course.title,
      '</a>'
    ].join('');
    wcLeft.appendChild(lastAccessed);
    sectionCreating = false;
  }

  function getLastAccessedCourse() {
    if (!storageKey) return;
    try {
      var stored = localStorage.getItem(storageKey);
      if (!stored) return;
      var course = JSON.parse(stored);
      if (course && course.title && course.url) {
        updateSection(course);
      }
    } catch (e) {}
  }

  // ──────────────────────────────────────────────
  // CONTINUE LEARNING BUTTON — scrolls to Learner Access Widget
  // ──────────────────────────────────────────────
  window.tiScrollToLearning = function () {
    var target = document.querySelector('.dashboard-access__header');
    if (target) {
      target.scrollIntoView({ behavior: 'smooth', block: 'start' });
      return;
    }
    window.scrollBy({ top: 500, behavior: 'smooth' });
  };

  // ──────────────────────────────────────────────
  // INJECT CARD — uses MutationObserver to wait for dashboard header
  // ──────────────────────────────────────────────
  var observer = new MutationObserver(function () {
    if (window.location.pathname !== '/learn/dashboard') return;
    if (document.getElementById('ti-welcome-card')) return;
    var header = document.querySelector('.header--dashboard');
    if (header && header.parentNode) {
      header.parentNode.insertBefore(card, header.nextSibling);
      observer.disconnect();
      getLastAccessedCourse();
    }
  });

  // ──────────────────────────────────────────────
  // SPA NAVIGATION — re-inject card when returning to dashboard
  // ──────────────────────────────────────────────
  function checkPage() {
    var onDashboard = window.location.pathname === '/learn/dashboard';
    if (!onDashboard) {
      trackCourseIfOnCoursePage();
      var existingCard = document.getElementById('ti-welcome-card');
      if (existingCard) existingCard.parentNode.removeChild(existingCard);
      var oldSection = document.getElementById('ti-last-accessed');
      if (oldSection) oldSection.parentNode.removeChild(oldSection);
      sectionCreating = false;
      try { observer.observe(document.body, { childList: true, subtree: true }); } catch (e) {}
    } else {
      setTimeout(getLastAccessedCourse, 900);
    }
  }

  window.addEventListener('popstate', checkPage);
  var originalPushState = history.pushState;
  history.pushState = function () {
    originalPushState.apply(this, arguments);
    setTimeout(checkPage, 100);
  };
  var originalReplaceState = history.replaceState;
  history.replaceState = function () {
    originalReplaceState.apply(this, arguments);
    setTimeout(checkPage, 100);
  };

  // Start observer
  observer.observe(document.body, { childList: true, subtree: true });

})();
</script>

Testing Checklist

• The welcome card appears below the dashboard header with the correct greeting (based on time of day) and the learner's first name.

• If the learner has a value in the configured reference field (default: ref4), it appears as the product/context line on the card.
  
  

  

If the learner has no first name set, the greeting falls back to "there" (e.g., "Good morning, there!").

• If the learner has no reference field value, the product line does not appear (no empty space or broken layout).

• The "Continue Learning" button scrolls to the Learner Access Widget.

• Navigate to a course, then return to the dashboard — the "Pick up where you left off" link appears with the course title and a working link.

• Test on mobile — the card stacks vertically and the geometric accent hides (responsive CSS is included).

• Navigate away from the dashboard and back — the card re-injects correctly.

Risk and Mitigation Strategy

• Any CSS or JavaScript added via custom scripts may not be supported by the Thought Industries Technical Support team. This is a custom implementation — document it internally and maintain it as part of your platform administration.

  • You can use a tool like Visual Studio to store your code internally. 

• The script depends on TI's DOM structure and CSS class names (.header--dashboard, .dashboard-access__header). Platform updates may change these. Test after every platform update.

• The script depends on window.CONF.preload.currentUser for learner data. If TI changes this data structure, the personalization features will break. The script uses try/catch blocks for graceful failure — the card will still render with fallback values.

• localStorage is browser-specific. The "Pick up where you left off" feature does not persist across browsers or devices, and clears if the learner clears browser data.

• The script overrides history.pushState and history.replaceState. If other custom scripts on your instance do the same, test for conflicts.

• The welcome card is injected via DOM manipulation, not TI's native widget system. It will not appear in the layout editor and cannot be repositioned using the drag-and-drop builder. To change its position, modify the JavaScript that targets the .header--dashboard insertion point.

• Document your customizations. When modifying colors, text, reference fields, or class names, note what you changed and why so future admins can maintain the script.

• The custom script can be localized using third party tool.

I'm looking for guidance on how to programmatically set or update a specific course status for a learner via the Thought Industries API.

Our use case: we occasionally need to reset or manually assign a course status (for example, forcing a course back to Not Started, or flagging it as In Progress) for individual learners, as part of an automation workflow.

I've explored the learner enrollment and progress endpoints in the API docs but haven't found a clear method for writing a specific status value to a learner's course record. The read side seems well documented, but the write/update side is less clear to me.

Specifically, I'd love to know:

1. Is there an API endpoint that accepts a course status value for a given learner and course?

2. What are the accepted status values (e.g. not_started, in_progress, completed)?

3. Are there any permissions or conditions that restrict what can be set via API (e.g. if SCORM completion is involved)?

Any examples, endpoint references, or workarounds from those who've tackled this would be really appreciated. Happy to share back what we end up implementing.

Thanks in advance!