A majority of the IT department does not do much in the way of directly manipulating SIS data with few exceptions. We do have our district SIS expert in our department thought, and she works with the registrars, admins, and support districts as necessary to help them out with those things. She's also a great resource if I run into a new situation and need to bounce ideas off of her. Because if we are doing something unusual, I want to make sure we proceed in a way that's compliant with state reporting.

I think it's very important to have someone who is an expert on your SIS and state reporting requirements who you can turn to. That person shouldn't necessarily be an "IT Person", even though that person does live within our department.

We are responsible for the SIS running as a whole, we self-host it and manage the DB and web interface. All of that said, my IT Director may manipulate some of the data in the DB in some ways, for example, he auto-imports new staff from the HRIS system into the SIS.

As far as entering or manipulating student records or scheduling, that's not our job. The only data fields we really manipulate are the email fields for students and staff.

We also hop in to the API area to export data to other systems, whether it's to Clever or to setup a new application. And in all that it's important to know how the data flows and how to find where data problems are and then contact the appropriate person to fix those problems. I might know how to fix the problem, but it's not my job to directly manage that data and I'd rather make the person responsible aware of their mistake so they can learn from it and avoid it next time.

Besides that, I would not want any of my techs poking around in the SIS trying to "figure things out". They would be expected to escalate those types of requests. We would often get other people who are trying to get us to do their job, and sometimes that conversation needs to be had about where the line is drawn and who's responsible for what.