Introduction
Evaluate Red Flag Mania’s LTI 1.3 launch model, current provider gates, and security boundaries before access opens.
A school should be able to evaluate the integration, prepare its systems, and understand the security model before an RFM account exists.
What these docs cover
These guides explain the approved LTI 1.3 learner-launch contract and the current Canvas and Brightspace release gates.
They are written for school developers, LMS administrators, and security reviewers. No RFM account is required to read them.
- How RFM validates an LTI 1.3 resource-link launch.
- How an LMS link stays pinned to one published RFM course version.
- What data is public, institution-scoped, or never shared.
- Which provider and environment paths are currently available.
The current entry path
Start with your LMS provider and choose staging, production, or both under one institution onboarding. When the Request access action is available, an institution developer or LMS administrator can submit that intent without entering LMS credentials or identifiers.
- 1
Review the core LTI 1.3 launch and security model.
- 2
Confirm the current status of your LMS provider.
- 3
Identify where an isolated test can happen: a separate sandbox, a restricted production tenant, or a location still to be confirmed.
- 4
Submit one institution request. One approval and invitation cover the selected environments.
One onboarding does not combine technical trust. Each selected LMS/RFM environment keeps its own registration and verification. This site never collects passwords, private keys, tokens, raw launch messages, or learner data.