# data[].attributes.body
First thing, I'm going to create and publish a "Statement of Accessibility". Also, I will update documentation (AR or internal MEMO) related to who the website admins are and the rules they must follow.

# data[].attributes.body
http://wave.webaim.org/

# data[].attributes.body
We provide admin access to all teachers on their laptop.

# data[].attributes.body
All teacher desktops have admin access to their station. Helps with getting work order tickets done faster and we haven't had a major incident stemming from this policy as of yet.

# data[].attributes.body
Teachers devices in general, do not have admin access.

# data[].attributes.body
We provide admin access to all teachers websites. Assist in technical issues with educational based programs.

# data[].attributes.body
Each user has admin access to their assigned devices. Site tech admins also have admin access.

# data[].attributes.body
We provide admin access to "certain" individuals - in most cases local administrative privileges are limited.

# data[].attributes.body
Teachers, Office Staff, and Admins have admin access...but we have district policies in place so that unauthorized software is not installed....yeah right.

# data[].attributes.body
Teachers do not have admin access unless we receive a request from their Principal or Supt.

We use SCCM for application deployment

# data[].attributes.body
MS Service Center

# data[].attributes.body
Bobbin Gravina

# data[].attributes.body
Teachers and Office staff have admin rights

# data[].attributes.body
There is a recommended list, but they can also install themselves.

# data[].attributes.body
They have access to install extensions and other things for Google. We are a Google environment. They do not have access to manage users or reset passwords. We do manage student devices on a granular level (ie: blocking who logins in, what sites, etc)

# data[].attributes.body
Whitelist only. VPN incident proved it was too easy to download apps and extensions.

# data[].attributes.body
In general, we allow for apps and extensions to be installed (Staff/Students). With a few exceptions in certain classrooms at our high school. After misuse detected (VPN/Proxy).

# data[].attributes.body
At the current moment, our director wanted everything allowed and decided to block apps and extensions as needed.

# data[].attributes.body
Students are limited to what they can install. Teachers can install extensions and apps.

# data[].attributes.body
Teachers can add apps to assigned laptops, but can not add to student or other devices.

# data[].attributes.body
Teachers and staff have access to Google's app store. Students can only install white listed apps.

# data[].attributes.body
We have a delegated model for the administration of extensions. We don't allow teachers to install extensions.

# data[].attributes.body
MS & HS

# data[].attributes.body
What Angel said...

# data[].attributes.body
We've gone back and forth. Currently yes.

# data[].attributes.body
Students have access by time limit through a webzone. This is managed by their teacher. Those  who are not in Student VLAN have access to Youtube but no access to comments.

# data[].attributes.body
Allow for all...there’s nothing bad on YouTube!

# data[].attributes.headline
Ernie - ECESD   Only for staff who have signed our district's Acceptable Use Policy.  

# data[].attributes.subject
Ernie - ECESD   Only for staff who have signed our district's Acceptable Use Policy.  

# data[].attributes.body
We allow youtube for teachers; for students we allow Youtube restricted mode. using a DNS change.

# data[].attributes.body
Youtube is accessible everywhere and to anyone. Using GoGuardian, our teachers will be able to block YouTube access as needed on the Chromebooks, if needed. Teachers can block YouTube in the computer labs as needed with LanSchool.

# data[].attributes.body
Staff only.

# data[].attributes.body
Teachers should have access to Youtube. Students do not.