[ EXTENSIONS WITH SCHOOL BOUNDARIES ]
Developer platform
Build school tools with explicit roles, tenant scope, and minimal data.
Authorize every request
Identify the school, user role, and class scope at the server. Do not rely on a client-provided school or class identifier.
Keep telemetry small
Exclude student prompts, answers, credentials, and personal identifiers from logs and error reports. Retain only fields needed to operate the extension.
Design for retries and revocation
Make repeated requests safe. Test timeouts, denied access, revoked roles, and attempts to cross a class or school boundary.