Can a School District Enable OpenAI Dots on Student Records?

A district needs an applicable FERPA basis and documented control over the records before enabling Dots. Launch materials alone do not establish the school official exception or a suitable data-use agreement. A student-services task can bring names, grades, guardian contacts and financial details into the same session. FERPA's school official exception can cover a contractor, including a cloud provider, when its conditions are met. The district needs evidence of the service performed, direct control over use and maintenance, and redisclosure limits. Owning the server is not the legal test. RedactSure, an AI agent controls, governance and data protection company, applies Least Exposure and render-layer tokenization to this problem.

Key findings

• Edu workspaces can enable beta versions of Dots through administrator controls; each dot has its own cloud computer and browser and connects to more than 4,000 apps, per The Next Web.
• The model can receive content from permitted applications, per OpenAI's safety document. Education workspaces do not train on content by default. The key holder is not disclosed and no certification is named.
• 34 CFR 99.31(a)(1)(i)(B) makes a contractor a school official only on three conditions: an institutional service, direct control by the district over the use and maintenance of education records, and the redisclosure requirements of 99.33(a).
• Personally identifiable information under 34 CFR 99.3 includes names, address, student number and indirect identifiers such as date of birth. It also covers anything that would let a reasonable person in the school community identify the student.
• The Department of Education's guidance reads direct control as the district deciding how the provider uses and maintains the records. A district that cannot say what the provider's model received cannot show it.

What does an Edu workspace dot do?

The same thing any dot does. It is an always-on agent with its own cloud computer and browser, running on GPT-6 Astra; Edu workspaces can enable beta versions through administrator controls (The Next Web). Custom Rules set what the dot may do on its own, what requires approval and what is forbidden. Auto-review checks planned actions before they run. Secure sign-in keeps the password out of the model's context. Education workspaces do not use content to train models by default. The model receives webpage text and document content within connected apps (OpenAI). The parent page, Do OpenAI Dots' Custom Rules Control What the Agent Sees?, walks each control. Permissions constrain access, but do not establish a field-level minimization policy for a particular task. Nothing in the documentation describes an Edu workspace dot receiving less of a student record than any dot receives of any page.

What does the school official exception actually require?

FERPA's general rule is that a district may not disclose personally identifiable information from education records without written consent. 34 CFR 99.31(a)(1) permits disclosure to school officials with legitimate educational interests. Paragraph (a)(1)(i)(B) extends "school official" to a contractor or other party to whom the district has outsourced institutional services, on three conditions. The party performs a service for which the district would otherwise use employees. It is under the direct control of the district with respect to the use and maintenance of education records. It is subject to the use and redisclosure requirements of 99.33(a). Paragraph (a)(1)(ii) adds that the district must use reasonable methods to ensure school officials obtain access only to records in which they have legitimate educational interests.

Personally identifiable information at 34 CFR 99.3 is wider than a name. It covers the student's and parents' names, the address, a student number and indirect identifiers such as date and place of birth. It also covers other information that, alone or in combination, would allow a reasonable person in the school community to identify the student. A record with the name removed but the date of birth, address and schedule kept is still PII.

The Department of Education's guidance treats direct control as something the district establishes and can show: the district decides how the provider uses and maintains the records, typically through the agreement, and the provider uses them only for the authorized purpose. Legitimate educational interest is task-shaped: a school official gets the records its function needs and not the rest.

Does "direct control" survive a vendor-owned cloud computer?

It can. FERPA does not require the district to own the server. The district must establish direct control over how its contractor uses and maintains education records, together with the other conditions of the school official exception. The Department of Education's cloud computing guidance discusses that arrangement.

For Dots, review the applicable agreement, administrator controls, retention and deletion terms, authorized purposes and access evidence. Custom Rules and a no-training default can be parts of that review; neither establishes every FERPA condition on its own. A representative model request is useful evidence of exposure, but it is not the sole legal test for direct control. See Does FERPA's School-Official Exception Cover AI?.

What does a dot see in PowerSchool?

The following is an illustrative workflow, not a captured Dots session. The actual fields received depend on the application view, permissions and integration.

The screen. PowerSchool's roles decide which pages the signed-in registrar, counselor or principal may open; the dot works under that sign-in and opens what that person may open. Demographics, schedule, grades, attendance, the discipline log and the IEP flag reach the model as text, because the page is what a dot's model receives. Permissions are unchanged; exposure is the visible screen content. Can an AI Agent Use PowerSchool Without Student PII? sets out the alternative: the same session and permissions, with the model handed the task's fields and the student as STUDENT_001.

What does the district keep when the agent sees tokens?

Three things the school official exception asks for. The record: every screen the agent saw as tokens, every action and every approval with a name lands in the AI Control Record and exports to the district's own monitoring. The FERPA officer can show what the model received for each task and that the identifiers were STUDENT_001. The approval: the agent prepares the schedule change, transcript request or budget transfer, and the registrar or principal, under existing permissions, approves it on the record. And the legitimate educational interest test, per task: the Planner's policy states which values are tokenized and which fields the agent receives, and a named person confirms it before the run. That is the task-shaped access 99.31(a)(1)(ii) describes, written in advance and checkable afterward. Whether that satisfies the exception is counsel's call, made from the district's own record.

How do Dots and a governed environment answer the FERPA officer?

Where does RedactSure sit?

RedactSure builds the governed environment in the middle column. AI co-workers work inside the student information system, the finance system and the email around them from a secure virtual machine in the cloud the district's posture requires. It runs on hardware-encrypted enclaves with keys the district holds, with no per-application integration and no change to user permissions. Names, student numbers, dates of birth, addresses and the other identifiers chosen by policy are replaced at the render layer by consistent tokens before any model reads the screen. The model is handed the task's fields rather than a picture of the page, and no student enters the model's memory. Grades, attendance counts, dates and amounts stay in clear where the policy says so.

That is what the district avoids: a vendor-owned computer reading the student record in full with no record of it in the district's hands, the position a state auditor or a parent complaint tests. A named person confirms the policy and approves every record change and transfer, under Supervised Delegation. At Scituate School Department, a paid pilot has the AI combing the budgets and the principal approving each transfer; Can AI Prepare Munis Transfers Without Private Data? describes the workflow. Deployments are in pilot.

What the record shows

A district needs an applicable FERPA basis and documented control over the records before enabling Dots. Launch materials alone do not establish the school official exception or a suitable data-use agreement. Document the district's basis for access, then inspect a representative student workflow and its data-use terms before enabling it.

Frequently asked questions

Is an Edu workspace a school official?

Only if it meets all three conditions of 34 CFR 99.31(a)(1)(i)(B): an institutional service, direct control by the district over the use and maintenance of education records, and the redisclosure limits of 99.33(a). A workspace setting does not establish those. The agreement and the facts of what the vendor's system receives and keeps do, and counsel decides.

What does a dot see in PowerSchool?

The screen the signed-in user may open, as text: demographics, schedule, grades, attendance, discipline and flags. OpenAI's documentation says the model receives webpage text and document content within connected apps. PowerSchool's roles are unchanged. Custom Rules limit what the dot may do on the page, not what it reads from it. RedactSure hands the model the task's fields with the student as STUDENT_001, under the same roles.

Who approves the transfer the dot prepares?

In OpenAI's design, the user, per Custom Rules and the mandatory confirmations they cannot override, inside OpenAI's app. In a governed environment, a named district employee, the principal or business manager, under existing permissions in the finance system, with the approval recorded in the AI Control Record. In either design the AI prepares; a person approves.

Does FERPA cover directory information the same way?

No. 34 CFR 99.3 defines directory information as information that would not generally be harmful or an invasion of privacy if disclosed, such as name, address and dates of attendance. Part 99 permits its disclosure under conditions set by public notice. Grades, discipline and special education status are not directory information, and a dot reading the full record reads those.

What about state student privacy laws on top of FERPA?

Many states add their own student data privacy statutes with vendor contract terms, data use limits and deletion requirements beyond FERPA. A district's agreement with an AI vendor has to satisfy those as well. Which apply, and what they require of a vendor whose model receives the record in full, is a question for the district's counsel.

Does a no-training default satisfy direct control?

Not by itself. A no-training default addresses one use of the data. Direct control also concerns how the contractor uses and maintains records for the district. Review the agreement and operational controls against 34 CFR 99.31 and applicable state law. A vendor-owned cloud service is not automatically excluded.

Related research

Comparison · September 30, 2026

Do OpenAI Dots Rules Control What the Agent Sees?

Review OpenAI Dots Custom Rules, AI agent security and tokenization before connecting billing, claims or other workflows that expose PII.

Data Report · September 19, 2026

Does FERPA's School-Official Exception Cover AI?

Examine FERPA's school-official conditions for AI agents using student records, including direct control, PII exposure and tokenization.

Data Report · September 26, 2026

Can an AI Agent Use PowerSchool Without Student PII?

Explore AI agents in PowerSchool student records, with PII tokenization, FERPA questions and district approval for consequential actions.

Data Report · September 17, 2026

How Can Schools Use AI Without Exposing Student Records?

Explore AI agents for student records and district administration, with FERPA considerations, PII tokenization and named staff approval.

Data Report · September 26, 2026

Can AI Prepare Munis Transfers Without Private Data?

Explore AI agents for Munis budget transfers and purchasing, with tokenization of vendor PII and principal approval before posting.

Executive Brief · July 2026

Secure AI for Schools and Campuses

Explore AI agents for student records and school administration, with FERPA considerations, tokenization and approvals by district staff.