For Admins
This guide describes how to register a Learning Management System (LMS) as a Learning Tools Interoperability (LTI) 1.3 issuer in Vocareum, and then attach the LMS-generated Deployment ID to that issuer. It is the Vocareum-side companion to every per-LMS setup guide: after the LMS-side registration produces a Client ID and Deployment ID, the steps below record those identifiers in Vocareum so that LTI launches from the LMS are recognized and accepted.
Two scopes are supported. Org-level registration is the recommended path for most institutions and covers every Vocareum course in the organization from a single entry. Course-level registration limits an LTI configuration to a single Vocareum course and is used when a per-course integration is required. For a full discussion of when each scope is appropriate, refer to What Is LTI 1.3 Integration with Vocareum?.
Field values (Issuer, Platform KeySet URL, OIDC Authentication URL, OAuth Token URL, and OAuth Server URL) are documented separately, per LMS, in LTI 1.3 Configuration URLs and Fields. This guide describes where to click; the reference describes what to enter.
Which scope do I need?
Most institutions use org-level registration. It is set up once by a Vocareum Org Admin, applies across every Vocareum course in the organization, and lets instructors add Vocareum to LMS courses without further admin involvement. Course-level registration is used for pilot programs, strict access limits, or per-course isolation, and requires repeating the registration for every Vocareum course.
For guidance on choosing between the two, refer to What Is LTI 1.3 Integration with Vocareum?.
Prerequisites
Before beginning, confirm the following.
Vocareum Org Admin access. Both org-level and course-level registration require organization-scoped permissions.
The Client ID and Deployment ID generated by the LMS during tool registration, along with the LMS-side URL values (Issuer, Platform KeySet URL, OIDC Authentication URL, OAuth Token URL, and, if the LMS requires it, OAuth Server URL). For instructions on producing these values in your LMS, refer to the applicable per-LMS setup guide:
For the exact value to enter into each Vocareum field, refer to LTI 1.3 Configuration URLs and Fields.
Org-level registration
Org-level registration is the recommended path. It creates one issuer entry and one (or more) deployment entries at the Vocareum organization scope, and covers every Vocareum course in the organization.
Adding the issuer
Follow these steps to register the LMS as an issuer at the organization scope.
From the Vocareum Dashboard, click Edit Org to open the organization settings.
Scroll to the Authentication section. Under LTI 1.3, click Issuers.
On the LTI 1.3 Issuers page, click New Issuer in the top right.
Fill in the issuer entry form with the values from your LMS, then click Save. For each field's expected value and the per-LMS specifics, refer to LTI 1.3 Configuration URLs and Fields.
Adding the deployment
The deployment attaches the LMS-generated Deployment ID to the saved issuer entry. Complete the steps in the previous topic before beginning here — a deployment cannot be added to an issuer that has not been saved.
On the Editing LTI issuer entry page for the issuer you just saved, click Deployments in the top right.
Click New Deployment.
Paste the Deployment ID copied from your LMS and click Save.
If your LMS supports multiple deployments per Client ID and you need to register additional deployments under the same issuer, repeat the steps above for each Deployment ID.
Course-level registration
Course-level registration attaches an issuer and deployment to a single Vocareum course rather than the organization. Use this scope when the integration must be limited to one course, such as during a pilot or for a strict access-control requirement. For general guidance on choosing between org-level and course-level, refer to What Is LTI 1.3 Integration with Vocareum?.
For Canvas, course-level Vocareum integration is now legacy. New Canvas setups use org-level registration together with Canvas Exceptions to limit availability instead. Refer to Setting Up LTI 1.3 for Canvas for the current Canvas flow.
Course-level registration takes place inside the Vocareum course's LTI Settings page rather than in Edit Org, and uses the Add/Edit LTI 1.3 Course Issuer/Deployment modal. The fields on the issuer form are identical to the org-level form; refer to LTI 1.3 Configuration URLs and Fields for values.
Adding the issuer at course scope
Follow these steps to register the LMS as an issuer scoped to a single Vocareum course.
From the Vocareum Dashboard, open the Vocareum course to be integrated with the LMS.
Open Course Settings and select LTI Settings from the left navigation.
Enable the LTI toggle and set LTI Version to v1.3.
In the top right of the LTI Settings page, click Manage Course-Level Access. The Add/Edit LTI 1.3 Course Issuer/Deployment modal opens.
In the modal, click Add Issuer in the bottom right.
On the Add New Issuer tab, fill in the issuer entry form with the values from your LMS, then save. For each field's expected value and the per-LMS specifics, refer to LTI 1.3 Configuration URLs and Fields.
If an issuer for the same LMS has already been registered at the organization scope or on another Vocareum course, select the Use Existing Issuer tab in the modal instead of filling in a new issuer form. The existing issuer's identifying values are reused, and only a new Deployment ID scoped to this course must be added.
Adding the deployment at course scope
The deployment attaches the LMS-generated Deployment ID to the course-scoped issuer entry. Complete the steps in the previous topic before beginning here — a deployment cannot be added to an issuer that has not been saved.
In the LTI Settings page for the course, click Manage Course-Level Access again to reopen the Add/Edit LTI 1.3 Course Issuer/Deployment modal. The issuer saved in the previous topic is listed in the table.
In the Deployments column for the new issuer's row, click Manage. The Add Deployment modal opens.
In the New Deployment ID field, paste the Deployment ID copied from your LMS, then click Add Deployment ID.
Repeat the entire course-level registration process for each additional Vocareum course that requires its own LTI integration.
Common issues
The tips below are specific to the Vocareum-side registration flow. For value-formatting issues (trailing slashes, extra spaces, the correct fixed vendor Issuer value, and so on), refer to the "Common gotchas" section of LTI 1.3 Configuration URLs and Fields.
The Client ID or Deployment ID must exactly match the value generated by the LMS. Even a single leading or trailing space, an invisible whitespace character, or a wrapped-line paste error causes the launch to fail. Copy and paste each identifier directly from the LMS rather than re-typing.
A deployment cannot be added to an unsaved issuer. Save the issuer entry first. In the org-level flow, the Deployments button appears on the saved issuer's edit page. In the course-level flow, the Manage button appears in the modal's issuer table only after the issuer row exists.
Course-level issuer entries are separate from org-level issuer entries. A course-level registration does not appear under Edit Org → Authentication → LTI 1.3 → Issuers, and an org-level registration does not appear in a course's Manage Course-Level Access modal. If a course is unexpectedly failing to launch, confirm the registration exists at the scope you intended.
Next steps
With the issuer and deployment registered, enable LTI 1.3 on each Vocareum course that will be launched from the LMS. For the course-side configuration steps and per-assignment LTI settings, refer to Configure LTI 1.3 in Your Course.