Formerly listed as a PD certificate resource.
A guided FERPA and SPED basics path a team can complete during onboarding, with a sample certificate format you can adapt for your own PD records. The point is not a credential from us: it is a documented, repeatable way to confirm that everyone who logs behavior data understands access, sharing, and revocation before they touch a real student record.
What the path covers
The path walks through the privacy fundamentals that matter for daily behavior data: who can view a student, how role-based access works, what families see in the parent portal, and what becomes part of the student record. It is grounded in the privacy article rather than abstract policy, so staff finish knowing how the rules show up in the actual workflow. District policy, NDPA, DPA, and your state addendum remain the source of truth.
Parent access and revocation, done right
A core section covers creating labeled parent access links, confirming what is exposed in a family-facing view, and revoking access the moment contact or custody changes. Staff should leave able to explain that revocation is immediate and that sensitive notes stay out of family views unless the team intended to share them. This is the part most likely to surface in a complaint, so it earns extra time.
Exports, records, and retention
Clarify which artifacts, such as PDF progress reports and communication logs, become part of the student record under your district's policy and how long they are kept. The software supports the workflow, but the district decides what counts as a record. Completing this section means staff understand that an export is not a casual screenshot, it is a document that may follow the student.
Use the certificate as onboarding evidence
Adapt the sample certificate with your district name, the completion date, and the staff member's role, then file it with your PD records. It is internal documentation, not an external accreditation, so keep the language honest about that. Having a dated record that each logger completed the privacy path is exactly the kind of evidence that helps during a compliance review.
Refresh it on a schedule
Treat the path as something new staff complete before they get logging access, and that returning staff revisit when policy or roles change. Tie a quick refresh to the start of the year or to any change in your sharing workflow. A privacy training that happened once two years ago is weaker evidence than a routine everyone repeats.