Introduction
Red Flag Mania integrations connect an institution’s systems to approved, published learning experiences.
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 LTI 1.3 launch path, the public values needed to begin, the security model, and the exact point where institution access is required.
They are written for the administrators and developers who need to bring Red Flag learning into an LMS with confidence.
- LMS administrators can follow provider-specific setup steps.
- Developers can inspect public protocols, flows, and data boundaries.
- Institution administrators can sign in when a connection must be attached to their institution.
Start with an outcome
Start with your LMS and use the provider guide that matches it. Each guide follows the same secure LTI 1.3 workflow, then calls out only the provider-specific steps.
- 1
Choose your LMS provider.
- 2
Create the tool in a test or beta environment.
- 3
Attach the registration to the correct RFM institution.
- 4
Validate in staging before production.
The public guide gives your technical team everything it can safely share. An authenticated RFM workspace begins only when a registration must be attached to your institution.
Public docs, authenticated operations
Documentation, public endpoints, supported claims, setup instructions, and capability status are available without an account.
Sign-in is required only when an action creates or exposes institution-scoped state.
- Public: guides, endpoint reference, launch model, security posture, and capability status.
- Authenticated: deployment records, institution identifiers, connection diagnostics, scoped credentials, audit history, and production enablement.