Configuring an LTI Provider connection requires administrator access on the Rise Up platform and access to the LMS administrator interface on the receiving platform.
The receiving platform must support the LTI 1.3 standard. Both parties must exchange configuration URLs and credentials during setup.
Access the configuration under Settings > Developer > Applications.
The LTI Provider feature enables Rise Up to act as a content source for third-party LMS platforms. Learners access Rise Up courses directly from the external LMS — authenticated via SSO — without a separate login. The course is displayed embedded inside the LMS interface, and progress and grades are reported back to the LMS automatically.
This feature supports the LTI 1.3 standard and covers: SSO launch, Deep Linking (course selection), and Assignment & Grade Services (progress passback).
Each LTI connection is associated with a Rise Up scope — either an internal scope or a specific client scope — which determines which users can launch through it and which courses are available for Deep Linking selection.
Key use case: organisations that manage learners in a separate LMS and want to deliver Rise Up content without migrating platforms.
- LTI 1.3 endpoints: Rise Up exposes the four required endpoints — OIDC Login Initiation, LTI Launch, Deep Linking, and JWKS. LTI messages are validated using a signature checked against the platform's JWKS endpoint. LTI 1.1 is not supported.
- SSO launch: learners access Rise Up content from the external LMS without a separate login. The course is displayed embedded inside the LMS via the embed_view=1 parameter.
- User identification: users are uniquely identified by the combination of issuer and subject (sub) from the LTI token, not by email.
- Just-in-time provisioning: if the learner has no Rise Up account, one is created automatically with first name, last name, username, client ID (or none for an internal scope), and the company's default language. No email is stored, and the account is flagged with the LTI signup origin. Users outside the connection scope are refused.
- Automatic enrolment: if the learner is not enrolled in the target course at launch, enrolment is created automatically.
- Grade and completion passback (AGS): Rise Up sends achieved score, maximum score, progress, and completion status back to the LMS when a learner completes an evaluated activity.
- Deep Linking: LMS administrators can browse and select Rise Up courses directly from the LMS interface during setup. The list of available courses is filtered to the client scope configured on the connection.
I — Create the connection in Rise Up
Setting up an LTI connection is a two-sided process: Rise Up generates the endpoints, and the LMS administrator enters them on the LMS side.
- Go to Settings > Developer > Applications. This page acts as a central marketplace for all active configurations, split into two categories: Integrations (HRIS, User Directory, external LTI tools) and LMS Publishing (LTI Provider connections), each showing a summary of what is currently active.
- Click Add connection [confirm UI label] in the LMS Publishing section.
- Enter a name for the connection and assign it to a Rise Up scope — an internal scope or a specific client scope. Optionally specify a client ID if required by the external LMS.
- Save the connection. The system generates the four Rise Up-side LTI endpoints, along with a public/private key pair for that client.
II — Share Rise Up URLs with the LMS administrator
From the connection detail view, copy and share the following endpoints with the LMS administrator:
- OIDC Login Initiation URL
- LTI Launch URL
- Deep Linking URL
- JWKS URL
III — Receive and enter LMS credentials
- The LMS administrator provides their platform's LTI 1.3 configuration data (Platform ID, Client ID, Authentication endpoint, JWKS endpoint, Access Token endpoint — exact labels vary by LMS).
- Enter this data into the Rise Up connection configuration.
- Save. The connection is now active.
IV — Grade and completion passback
Rise Up sends learner performance data back to the external LMS automatically when a learner completes an evaluated activity (via LTI Assignment & Grade Services). The following data points are sent:
- Achieved score
- Maximum score
- Progress status
- Completion status
Learner access is also fully automated at launch time:
| Scenario | System behaviour |
|---|---|
| Learner has a Rise Up account and is enrolled | Launch succeeds immediately. |
| Learner has a Rise Up account but is not yet enrolled | Enrolment created automatically. Launch proceeds. |
| Learner has no Rise Up account | Account created automatically (no email stored). Enrolment created. Launch proceeds. |
| Learner is outside the connection scope | Launch is refused. The learner cannot access the content. |
FAQ & Troubleshooting
-
Issue: Learners are refused access when launching from the external LMS.
Solution: Users outside the Rise Up connection scope are refused at launch. Verify that the learner's attributes match the connection scope configured in Settings > Developer > Applications. Also confirm the LMS is sending the correct user identifiers in the LTI launch message.
Issue: Grade and completion data is not appearing in the external LMS after course completion.
Solution: Passback is triggered when a learner completes an evaluated activity in Rise Up. Confirm the course contains an evaluated activity and that it was completed. Also verify the AGS endpoint is correctly configured on the LMS side and the connection uses the correct client ID.
Issue: The Deep Linking course selector shows no courses.
Solution: The connection must be scoped to a Rise Up scope containing published, visible courses. Verify that the scope assigned to the LTI connection has courses published and visible in the catalogue for the relevant user.
Issue: A user already exists in Rise Up with the same username but the launch is refused.
Solution: The existing user does not belong to the scope associated with this LMS Publishing connection. A user must belong to the connection's scope to launch through it — this is expected behaviour, not an error.
-
Which LMS platforms are compatible with LTI Provider?
— Any LMS that supports LTI 1.3. Common examples include Moodle, Cornerstone, SAP SuccessFactors, and Canvas. Configuration steps on the LMS side vary by platform. LTI 1.1 is not supported.
What user data is stored during just-in-time provisioning?
— Rise Up stores first name, last name, username, client ID (or none for an internal scope), and the company's default language. No email address is stored.
Can the same LMS support multiple LMS Publishing connections pointing to different Rise Up scopes?
— Yes. Each connection is configured independently with its own scope and optional client ID. Multiple connections coexist independently, even from the same LMS platform.
Can an instructor select any Rise Up course during Deep Linking?
— No. Only courses visible in the administration for that user and filtered by the connection's client scope are displayed in the selector.
Is progress reported in real-time or in batch?
— Passback is event-driven — triggered at completion of an evaluated activity. [Confirm timing and any delay behaviour with the technical team.] -
Contact Rise Up Support
Managing integrations and applications
Configuring SSO authentication
Managing perimeters and visibility