Supporting a Bring Your Own Device policy with classroom.cloud

Schools may choose to implement a Bring Your Own Device (BYOD) policy for various reasons, such as reducing school IT costs, environmental concerns, or allowing students to use their own devices where familiarity is needed. 

If you already use classroom.cloud for teaching and learning, could you also use it to support a BYOD policy? Let’s find out…

Configure - Organisation Settings

Configure

With classroom.cloud, your IT team configures all student devices from the web portal, regardless of whether they are school-owned or personal devices. So, once classroom.cloud is installed onto a student’s personal device, then that’s it! If you need to reconfigure, you can do it all centrally and seamlessly from the web portal.

Connect

The easiest way for students to connect to the class with their personal devices is to use classroom.cloud’s Class Code, as there will be no other standardized device name format or identifier (as on school-owned devices) to enable the device to sign in.

Connect 2 - Student side entering the matching class code for the History lesson
Student Register - Get Name

Student register

Teachers can request that BYOD students register into the class with their given names (rather than the login name of the device, often used in school-owned device setups), making it easier to see who is present.

iOS app

BYOD students using the iOS app can still use their school’s Google or Microsoft accounts, which is essential for classroom.cloud’s dedicated online safety tools to be able to safeguard them.

IOS app
Privacy Settings

Maintain privacy

classroom.cloud maintains students’ privacy on their personal devices, as the school can set the conditions for when the classroom management, safeguarding, and activity monitoring are active – based on the time, date, or network the device is connected to.  

Read our ‘Privacy’ policies here.  

Curious to find out more about how a BYOD policy could work with classroom.cloud in your school? 

with our team today.