Bring Your Classroom
Import existing classroom structures through a guided, reviewable workflow instead of silently creating duplicate instructional records.
Connected Systems
Bring Existing Classroom Systems into a Reviewed ClassLattice Workflow
Use browser capture, classroom imports, standards roster exchange, LTI launch, and Microsoft 365 connections without hiding review boundaries.
Why this workflow stays connected
ClassLattice makes connection boundaries visible: staged imports require review, launches preserve authorized context, and source material remains identifiable inside the teaching workflow.
Core capabilities
Google Classroom and Microsoft 365
Connect common educator ecosystems for supported import and sharing workflows while keeping the ClassLattice record reviewable.
LTI Launch
Use authorized launch context to enter the appropriate ClassLattice workspace and activity boundary.
OneRoster Staging
Stage roster data for validation and approval before it changes live classroom access.
Workflow comparison
| Capability | Disconnected workflow | ClassLattice |
|---|---|---|
| Import behavior | Immediate or opaque mutation | Staged review before commitment |
| Launch context | Generic deep link | Authorized course and activity context |
| Source lineage | Often lost after import | Retained in connected records |
| Admin visibility | Vendor-dependent | Explicit connection state and boundary |
Frequently asked questions
Does every integration provide two-way synchronization?
No. Capabilities differ by connection. ClassLattice describes the supported import, launch, or sharing boundary rather than implying universal two-way sync.
Can roster data change live access immediately?
OneRoster data is staged for validation and approval before commitment, helping administrators catch mapping issues first.