[ PLAN A SUPPORTED DEPLOYMENT ]
School system requirements
Confirm identity, networking, provider, browser, storage, and operating ownership before rollout.
Access and identity
Provide supported student and staff identities, assign school roles, and define who maintains class membership and revocation.
Network and provider access
Allow required school web access and the approved model-provider endpoints. Keep provider credentials in protected server configuration.
Operations
Assign owners for database backups, updates, monitoring, incident response, and support. Validate requirements against the deployment package your school will use.
Check the school's actual environment
Use a current browser with JavaScript enabled and access to the school workspace. Test the school's identity provider and network rules on a managed student device. Browser extensions, content filters, and blocked third-party sign-in can affect the result.
Test an ordinary learning session
Sign in, choose a class, select an approved model, send a short question, attach an allowed file, and reopen the conversation. Repeat the test on the device and network students will use. Confirm that keyboard navigation and text scaling remain usable.
Plan provider and source access separately
The service needs access to configured model providers and document sources. A healthy web page cannot compensate for expired source credentials or an exhausted provider balance. Assign an owner for those dependencies before rollout.