Policy committee reviews consolidated acceptable-use draft, district cell‑phone rules and AI guardrails

The Niskayuna Central School District Policy Committee met March 18 and heard a staff presentation on a consolidated Computer Network Acceptable Use policy that would replace several older IT policies and be supported by separate regulations for student use, staff use and student cyber‑violation responses.

Gus, a district staff member who led the presentation, said the approach was to move from “a little bit scattered” policies to “a single overriding policy that will govern all of the acceptable use of computers within the district.” He said the district intends to publish follow‑up regulations addressing student acceptable use, staff acceptable use and procedures for handling student cyber violations.

Committee members said the consolidation would simplify policy searches and compliance. “In the past…you had to go to 4 or 5 different places,” one committee member said during the meeting, endorsing the streamlined approach.

Staff previewed several implementation details. Under the draft cell‑phone provisions, the superintendent would identify positions eligible for a district‑issued phone. Some roles would be required to carry a district device; others could opt for a stipend to use a personal device. Gus said the policy would require multi‑factor authentication and district apps such as ParentSquare on district‑managed devices. On personal devices used for district business, he said, “the new acceptable usage policy is written as anytime you're using a corporate resource, it will apply.”

Committee members asked whether personal devices used for district business could be subject to Freedom of Information Law (FOIL) requests and how searches would be handled. A staff response clarified that the district’s focus would be on retrieving district accounts and data (for example, district email) rather than searching the contents of a personal device itself; “we're not searching the phone. We're searching the email account, which we have access to in the back end,” Gus said.

The presentation also described the district’s layered web filtering. Staff said Cisco Talos contributes global threat and category lists that inform the district’s umbrella filtering, with an additional student filter layer managed by the district that can allow or block specific sites. Staff reported that teacher requests for site exceptions vary and estimated the volume at “from 0 to 10” requests in a given day depending on teaching needs.

Committee discussion turned to generative AI. Staff framed AI as “another tool” and said the draft policy points teachers and students back to the district code of conduct and to locally developed AI “guardrails.” Gus explained the district’s instructional stance with an “80/20” guideline: “it may give you 80% of the work, but the 20% needs to be your own,” meaning students should review, edit and understand AI‑generated content before submission.

Members raised concerns about copyright, the potential for students to use proprietary or unpublished material in AI inputs, and equity of access. Jess, identified in the meeting as a teacher practitioner, said she had “some personal thoughts about AI, but I do see the benefit” and asked whether the district would provide training and classroom supports. Staff said faculty training and digital‑citizenship curriculum resources are being considered and that the district has piloted exercises with teachers to develop practical guardrails for classroom use.

Committee members asked that the guardrails and related guidance be made available to families as part of district communications so that parents can reinforce expectations at home. Staff agreed that parent resources or workshops could be useful.

On timing and next steps, staff reiterated that the consolidated acceptable‑use policy had not been substantially updated since 2017 and that the proposed approach would place regulations on the district website while the board would continue to approve policies. Committee members indicated informal agreement to advance selected items: staff were directed to prepare follow‑up regulations (student and staff acceptable use and cyber‑violation procedures) and to advance specified policy letters for a first read at the upcoming board cycle.

The committee set the next policy committee meeting for May 13.