-  OneRoster Compatibility
 TCM Learning Platform is able to ingest and sync user/class data via the OneRoster standard.
-  Self-Roster Capability
 Customers should have the option to manually add or update teachers, classes, and students through a self-service interface.
-  CSV/Template Upload
 For districts that prefer traditional batch uploads, TCM accepts a standardized CSV template.
Role of IT Admin
Single Sign-On Support
-  ClassLink & Clever Integration
 TCM Learning Platform supports both ClassLink and Clever APIs, enabling auto-provisioning of users and seamless login from those portals.
-  Google Classroom Federation
 If a district already uses Google Classroom, teachers/students can log into TCM with their existing Google credentials.
-  Direct Login (Username/Password)
 In environments without an SSO provider, users can register for TCM directly using email/password authentication with basic password-reset flows.
LMS Support
- Schoology integration supported out of the box
- LTI 1.3 LMS supported via integration
District-Level Administrator Assignment
- Before any teacher or student can register, the district must designate at least one “District Administrator” account.
Teacher–Classroom–Student Hierarchy
- TCM Learning Platform’s data model enforces a strict relational structure:
1. Classroom → 2. Teacher → 3. Student
- Every student must belong to at least one classroom, and every classroom must be owned by a teacher.
School Administrator Presence
- Each school must have at least one “School Administrator” in TCM Learning Platform before rostering or SSO can be fully enabled.
- If a campus has no existing administrator, TCM will create a “placeholder” school admin account. Credentials shared upon request.
Customer-Side Technical Skill Set
-  To connect a district’s existing SIS/SSO systems to TCM Learning Platform, customers must have at least one in-house IT contact who:
- Understands basic CSV formatting (for template uploads).
- Can work with the SIS vendor or internal data team to extract roster files.
- Can liaise with TCM’s technical support during API or SSO integration.
 
Mandatory Technical Onboarding Meeting
- Before any data flow or SSO link is activated, TCM schedules a one-hour onboarding session (video-conference) with the customer’s IT lead and at least one district or school administrator.
-  During this session, TCM’s integration engineer will:
- Review the rostering method selected (OneRoster vs. CSV vs. self-roster).
- Validate SSO credentials (API keys, service account details, or direct login settings).
- Confirm that the district administrator and school administrators are correctly configured.
- Walk through any custom license-start-date settings.
 
Template-Based Rostering Data Adjustment
- Customers opting for the CSV/Template Upload method must format their roster data to match TCM’s prescribed template.
- TCM will provide the template file (including field definitions and sample rows) and offer assistance (via email or short screen-share sessions) to finalize any formatting questions.
Full-File Updates for Rostering and SIS Changes
- When sending roster updates via CSV/Template or SIS-based sync, customers must include the entire dataset (all teachers, classes, and students) along with any changes.
- Submitting only delta or incremental records will cause The TCM Learning Platform to treat missing entries as deletions, resulting in unintended user/data loss.
- Districts should plan their routine exports to always provide a full extract rather than just modified rows.
Roster Only Active Users
- Customers should share only those teachers, classrooms, and students who will actively use The TCM Learning Platform—not the entire district user list.
- Uploading the full district roster can lead to unnecessary license consumption and higher costs.
Single Role Enforcement
- TCM Learning Platform supports exactly one role per user account (e.g., a teacher account cannot also serve as the district administrator).
- If an individual requires multiple responsibilities, they must be assigned separate accounts with a unique email address for each role.
Possible Rostering and SSO Combinations
- LTI-compliant LMS + SSO via LMS
- ClassLink Roster + ClassLink SSO
- Google Classroom Roster + Google Classroom SSO
- OneRoster 1.1 + Manual Login using Default Password
- OneRoster 1.1 + Clever SSO
- OneRoster 1.1 + SAML SSO
 
