
Can Schools Enable OpenAI Dots on Student Records?
Assess OpenAI Dots for student records, FERPA obligations and AI agent access before connecting PowerSchool or other district systems.
Research topic
Research on FERPA for AI agent workflows, with tokenization, access controls and evidence for teams handling sensitive business data.

Assess OpenAI Dots for student records, FERPA obligations and AI agent access before connecting PowerSchool or other district systems.

Run one workflow and one record type with a page policy that replaces identifiers, a named approver and a reviewed record. Check it completes on tokens.

Treat the agent and its model provider as a school official under direct control, and keep education record PII out of the model. Check what it sees.

Notification clocks, regulator reviews, fine tiers and contract consequences run in order, whether a person or agent caused it. Keep PII out of the model.

The named person already accountable for releasing that data, such as the records custodian or account owner, not the AI team. Check each send goes there.

The data owner and classification policy should, per agent and destination, with the decision recorded; in practice the builder or an inherited login does.

No, not while the agent reads the real inbox, because every parent's message in a teacher's mailbox reaches the model's context and a reply about one child can name another. Ask what the model receives from the rendered inbox, and whether other families' names, addresses and student identifiers reach it as tokens.

No. An enrollment screen prints the student's date of birth beside the packet, so an agent working that record reads what the certificate proves even when it never opens the scan; ask for consistent tokens on those fields and a packet the model cannot render.

No. The Social Security number sits on the identity page as a field the role can open, and an agent working that page receives whatever the screen renders, so the answer changes only when the value is replaced with a consistent token before the model reads it.

No, not while the agent reads the gradebook: a student record is a FERPA education record, and a model that opens the screen receives the name, grades and support plan beside the attendance facts. Require consistent tokens on the rendered page, a named person's approval of each record change, and a record of what the model received.

No. A financial aid file is built from the FAFSA, and the screens that process it show the student's Social Security number beside parent income, so an agent working a verification file reads both; ask for placeholders on that screen and a named approver on every award.

Everything the student profile renders: the legal name, date of birth, grade level, attendance history, grades, discipline entries, special education status, clinic notes and guardian contact details. Ask what the model receives from each rendered screen and who approves a change to the record.

On a gradebook the string is a key, and the model receives it beside the grades it opens, so the record behind the identifier travels with the run. Ask what the model was handed on the rendered page and whether a named person approved the change the agent submitted.

The model receives the grade with the student it belongs to, because a gradebook renders both, and a vendor that receives the pairing is an outside party under FERPA. Ask what the model receives from the rendered page, who approves a change, and whether the identity can be replaced with a stable token first.