Skip to main content
Once your LMS is connected to Exec, every roleplay activity you add to a course points at one or more Exec scenarios. There are two ways to wire an activity to its scenarios:
  • Pick scenarios from inside the LMS. If your LMS supports LTI deep linking (also called “content selection”), you launch Exec’s picker from the LMS course editor, browse or search your workspace’s scenarios, select one or more, and Exec sends them back as ready-to-use activities. No IDs to copy. Recommended when available — see Pick scenarios from inside the LMS.
  • Paste a scenario_id custom parameter. For LMSes without deep linking, or when you’d rather configure the activity by hand, you copy the scenario’s scenario_id from Exec and paste it into the activity’s custom parameters. See Add an LTI activity by custom parameter.
Either way, the LMS holds the activity wrapper (title, due date, gradebook column); Exec runs the actual scenario.

​
Pick scenarios from inside the LMS

If your LMS supports LTI 1.3 deep linking, you can pick Exec scenarios without ever leaving the LMS. Look for options in the course editor labelled Content selection, Deep linking, Select content, or Browse tool content when adding an external tool activity.
1

Add an external tool in your course and pick Exec

In your LMS course editor, add a new activity and choose “External tool” (or the equivalent). Select Exec from the list of preconfigured tools.
2

Open Exec's content picker

Click Select content, Browse, or the equivalent button. The Exec picker opens inside the LMS — no separate window, no re-login.You see the same scenarios you’d see when signed into Exec directly, filtered to what you have permission to view in the connected workspace.
3

Search and select scenarios

Use the search box and filters to find scenarios. Click a scenario card to select it; click again to deselect.If your LMS allows multiple items in a single deep-linking request (Canvas, Moodle, Blackboard, Brightspace), you can select several scenarios at once and Exec creates one LMS activity per scenario. If the LMS only accepts a single item, the picker enforces single-select automatically.
4

Confirm the selection

Click Add to course in the floating selection bar. Exec signs the selection and hands it back to the LMS, which drops the new activities into your course editor.Each activity is pre-titled with the scenario name; you can rename it, set a due date, or configure grading like any other LMS activity before saving.
Each deep-linking session is single-use and expires after 30 minutes. If you close the picker without confirming or the LMS times out, just click Select content again in the course editor to start a fresh session.
The activities Exec sends back already have the correct scenario_id custom parameter baked in — you don’t need to paste anything. Grade passback still requires that Assignment and Grade Services are enabled on the tool in your LMS (see Grade passback).

​
Add an LTI activity by custom parameter

Use this flow if your LMS doesn’t support deep linking, or if you want to wire an activity up by hand. Every LTI activity points at exactly one Exec scenario, identified by a custom parameter called scenario_id.

​
What you need before you start

  • The Exec scenario must already exist in the workspace that’s connected to the LMS.
  • You need the scenario’s scenario_id custom property — Exec gives you this with one click on the scenario page (see below).

​
Copy the custom property from the scenario page

Once you’ve connected at least one LMS, every scenario page in Exec shows the LTI custom property at the bottom for admins. Open the scenario in Exec, scroll to the bottom, and click Copy next to the LTI custom property row.
LTI custom property row at the bottom of a scenario page, showing "scenario_id=discovery-call-practice" with a Copy button
The copied value looks like scenario_id=discovery-call-practice — exactly what your LMS expects in the activity’s Custom parameters field. Paste it as-is.
The custom property row only appears for workspace admins, and only after at least one LMS is connected. If you don’t see it, connect an LMS first.

​
Add the LTI activity to a course

The exact menu names vary by LMS, but the pattern is always the same:
1

Edit the course and add an external tool / LTI activity

In your LMS course editor, add a new activity and pick “External tool”, “LTI 1.3 tool”, or whichever phrasing your LMS uses. Select Exec from the list of preconfigured tools.
2

Set the activity title

Use a title learners will recognize — e.g., “Discovery Call Practice” or “Objection Handling Roleplay”. This is the link text learners click in the LMS.
3

Paste the scenario_id custom parameter

Open the scenario in Exec, scroll to the bottom of the scenario page, and click Copy next to LTI custom property.Back in your LMS, find the activity’s Custom parameters field and paste. It should look like:
Each activity points at exactly one scenario. If you want to assign a learner three roleplays, add three LTI activities, each with its own scenario_id.
4

(Optional) Enable grade passback

To send roleplay scores back to the LMS gradebook, mark the activity as graded and pick a maximum score (Exec scales the percentage you earn against this value). The exact toggle varies by LMS — see Grade passback for details.If you added the activity through the content picker, some LMSes (notably Absorb) don’t ask Exec to suggest a gradebook column at picker time. Open the activity in the LMS after it’s added and set the points value manually to turn on grade passback.
5

Save the activity

Save and publish. Learners will now see a clickable activity in their course. When they click it, the LMS launches Exec, signs them in automatically, and drops them into the scenario.

​
What learners see

When a learner clicks the activity in the LMS:
  1. The LMS hands the launch off to Exec.
  2. If the learner has never used Exec before, an account is provisioned automatically and added to your workspace as a Member.
  3. They land directly on the scenario page, ready to start.
  4. If they aren’t signed in to Exec in their browser, they’re bounced through Exec’s login screen first; after signing in, they land on the same scenario.
The handoff link from the LMS is single-use and expires after 30 minutes. If a learner clicks the activity but doesn’t follow through, the link is silently invalidated — they can re-click the activity in the LMS to start fresh.

​
Pop-up vs. iframe launches

How the scenario opens depends on how the activity is configured in your LMS:
  • New window / pop-up launches open the scenario in a new browser tab and redirect automatically. Learners don’t see any Exec-specific intermediate screen.
  • Embedded / iframe launches (used by LMSes like Absorb and TalentLMS when the activity is placed inline in a course) show a branded Continue to Exec card inside the LMS frame. The learner clicks Continue to Exec once and the scenario opens in the top-level tab. This click is required by browsers — cross-site launches can’t auto-navigate the parent tab without a user gesture.
Both launch modes are supported out of the box once your LMS is connected. No extra configuration is needed on the Exec side to allow your LMS to embed the launch in an iframe — Exec derives that permission from your saved LTI connection.
If a learner is signed into Exec as a different user than the one their LMS account is linked to, Exec refuses to open the scenario as the wrong user. They’ll see an error asking them to sign out of Exec (or use an incognito window) and click the LMS activity again.

​
How user accounts get linked

Exec keys learner identity by (LMS issuer, sub) — the platform’s stable user ID — never by email. This means:
  • A learner whose LMS email later changes still maps to the same Exec account.
  • Two learners with the same email on different LMSes map to two distinct Exec accounts.
  • The first time a learner launches from your LMS, Exec checks whether the email already belongs to an Exec account. If it does, that account is bound to the LMS identity. If not, Exec provisions a fresh account.
Learners launched via LTI are added to the connected workspace as Members. Promote them to higher roles in Workspace settings → Users if needed.

​
Custom parameter reference

Exec recognises the following custom parameters on an LTI launch: If you’d like Exec to support additional custom parameters (e.g., for assignment groups or skill mappings), let us know.

​
Next steps

Grade passback

See how roleplay scores flow back into the LMS gradebook.

Troubleshooting

Diagnose launch failures using correlation IDs.

​
Getting Help

Need help wiring up a course? Contact us at [email protected].