Staff sign in with Google
Staff use the Google email already on the school roster. There is no separate GuidelineK12 password to create or share. Families do not get accounts. They receive the notices the school sends.
Security
GuidelineK12 holds school discipline records. This page describes how access, sign-in, and records work today. A data privacy agreement with your district is a separate document, signed as part of getting started.
For school leaders
Staff use the Google email already on the school roster. There is no separate GuidelineK12 password to create or share. Families do not get accounts. They receive the notices the school sends.
A teacher works with the incidents they report. A school admin stays in their school. A district admin can work across schools in that district. The people who administer GuidelineK12 itself are a separate, limited group.
When someone changes an incident, sends a parent notification, or changes who has admin access, GuidelineK12 keeps a record of that action. The wording of a parent letter is not copied into that record.
For technology departments
District Infinite Campus client secrets are encrypted at rest with AES-256-GCM. They are not shown in the app.
Those records live in the application database and rely on the database host’s encryption at rest. The application does not separately encrypt every student field.
Staff sessions last up to 12 hours. In production the site is served over HTTPS and session cookies are marked secure.
Responses include X-Frame-Options: DENY, X-Content-Type-Options: nosniff, a Content-Security-Policy, and HSTS in production. Authenticated pages and API responses are sent with Cache-Control: no-store.
We will walk through sign-in, roles, and Infinite Campus sync before you commit.