Skip to main content
LTI 1.3 (Learning Tools Interoperability) lets your LMS embed Exec roleplays as launchable activities inside a course. Learners click the activity in your LMS, sign in once via the LMS, and land directly in the assigned scenario — no separate Exec account or password required. When they finish, the score flows back into the LMS gradebook automatically. Exec implements the LTI 1.3 standard, so any LTI 1.3-compliant LMS should work. (LTI 1.1 is not supported.) Configuration is per workspace and admin-only — workspace admins set up the connection; everyone else just experiences single sign-on.
LTI 1.3 is available on the Professional and Enterprise plans. On Free and Starter workspaces the LTI settings page shows an upgrade prompt instead of the configuration UI. If your workspace already has connected LMSes from a previous plan, they remain listed on the page, but you’ll need to upgrade to add, edit, or generate new registrations.

What you get

  • Single sign-on from your LMS — Learners launching from the LMS are auto-provisioned in Exec and added to the workspace as a Member.
  • Per-scenario launches — Each LMS activity points at one Exec scenario, identified by its slug or ID.
  • Grade passback — When the roleplay is graded, the score posts back to the LMS as an Assignment and Grade Services 2.0 score on the activity’s lineitem. Best-of-N: the LMS only receives a score that improves on the previous submission.
  • Self-service setup — Admins connect an LMS from Workspace settings → Integrations without contacting Exec support.

Prerequisites

To connect an LMS to Exec you need:
  • A workspace on the Professional or Enterprise plan. Free and Starter workspaces can’t configure LTI. Upgrade from Workspace settings → Billing.
  • Workspace admin access in Exec. The LTI settings page is admin-only.
  • Admin access in your LMS with permission to register external tools or LTI 1.3 platforms.
  • Scenarios already created in your Exec workspace. LMS activities reference scenarios by slug or ID, so the scenarios need to exist before you wire them up in the LMS.

How it fits with other LMS integration options

LTI 1.3 is the deepest of three LMS integration options. Pick based on what you need:
SCORM is an import format, not an export format. Exec reads Articulate Rise SCORM exports so you can bring existing training in (see Import a Course), but it does not produce SCORM packages. There is no way to package a roleplay or an Exec course as a .zip and upload it into another LMS. LTI 1.3 is the supported path for putting Exec content inside your LMS.

Where LTI work shows up in Exec

Launching from your LMS does not move reporting into your LMS. Sessions run and are graded in Exec, and Exec is still where managers review them.

Sessions, not Assignments

A roleplay completed through an LTI launch appears under Sessions and feeds Analytics exactly like a session started inside Exec. Managers see the full transcript, the score, and the rubric breakdown. It does not appear under Assignments. That tab tracks only work assigned from inside Exec, so an LMS-driven program will show an empty Assignments tab even while sessions are piling up. Review LMS-launched work from Sessions or Analytics, filtered by person or group.

Assign in one system, not both

If you are assigning the activity in your LMS, you do not also need to assign the scenario in Exec. Doing both creates two records of the same work. Assign in the LMS, review in Exec.

Groups are what turn manager visibility on

The first time someone launches a roleplay from your LMS, Exec adds them to the workspace as a Member but does not put them in any group. Group admins only see people in their own groups, so a manager whose team arrived through LTI will see an empty dashboard until an admin adds those people to a group.
If a group admin reports that they can see nothing, this is almost always why. Two ways to stay ahead of it:
  • Build your groups before you launch the LMS activity, then add learners to them as they appear in Members.
  • Periodically filter the Members list by No groups to catch anyone who came in through a launch and has not been grouped yet.
Workspace admins see every session regardless of grouping, so this only affects group admins.

Learner & Admin Experience

This video shows both the learner and admin experience of integrating, building a course with an Exec Roleplay.

Next steps

Connect your LMS

Walk through dynamic registration or a manual connection.

Add roleplays to a course

Wire individual scenarios up as LMS activities.

Grade passback

See how Exec scores flow back to your LMS gradebook.

Troubleshooting

Diagnose launch failures using correlation IDs.

Getting Help

Need help with LTI setup? Contact us at [email protected].