Dyknow Transition: Securly Classroom Implementation Guide

Dyknow Transition: Securly Classroom Implementation Guide

Total time est: ~1.5 hours (15 minutes prework, 45 minute meeting, 15 minutes postwork)

Required attendees:

• Primary technical admin

• Google Workspace Super Admin (if you're using Google Classroom rostering)

Optional but helpful:

• Curriculum or instructional tech staff

• Building-level IT coordinators or coaches

• Teacher training contacts

Pre-Work: Complete before your implementation meeting

• Identify your teacher training contact (name, email, phone) - coordinates Securly Classroom professional development

• Confirm your roster source for Securly Classroom: Google Classroom, OneRoster, PowerSchool, Infinite Campus, Skyward, or another SIS/LMS

• Know what student devices are in classrooms: Chrome extension for Chromebooks; native agent for Windows or Mac

• Confirm whether you need BYOD support in Securly Classroom for student-owned devices

• Ensure the Google Workspace Super Admin who will link the account is available for this meeting

Questions we will answer in this meeting

Classroom deployment

• What roster source will Securly Classroom use? Google Classroom, OneRoster, or a direct SIS integration? What student devices are in classrooms? (Determines Chrome extension vs. Windows agent vs. Mac agent deployment.)

• If using Chromebooks: Who is the Google Workspace Super Admin who will authorize the Google integration in Securly Classroom Settings > Google Integration?

• Do you need BYOD support for student-owned devices in the classroom?

• Do you have co-teaching setups? If yes, which teachers share the same classes and need co-teacher access?

• What is your rollout plan - all schools at once, or phased by building?

What happens in the implementation meeting (step-by-step)

1. Securly Classroom account creation is confirmed. Do not deploy the extension until this is verified.

2. Securly is added as a Trusted App in Google Admin Console: Security > API Controls > Third-Party API Access > search for Securly > select Trusted.

3. The Google Workspace Super Admin links the account in Securly Classroom Settings > Google Integration > Link Account (requires Super Admin credentials).

4. Roster integration is configured (Google Classroom, OneRoster, or SIS direct). An initial roster sync is run and class lists are verified.

5. For Chromebooks: the Securly Classroom Chrome Extension is deployed via Google Admin Console to student OUs (Force Install + Pin). Permissions set to Allow All.

6. For Windows devices: the Securly Classroom Windows Agent MSI is deployed via GPO or software management tool.

7. For Mac devices: the Securly Classroom macOS Agent is deployed via MDM (Jamf, Mosyle, Securly, Intune, etc.).

8. Teacher access is confirmed: teacher accounts are imported from the roster sync and visible in the Securly Classroom dashboard.

9. Optional: Pre-configured blocking plans, scenes, or web link shortcuts are created for teachers to use from day one.

10. A pilot session is run with or as one teacher to confirm student devices appear and all teacher controls work.

11. Teachers receive access to Securly Learn for self-paced resources including role-specific training tracks. Live teacher training is scheduled via your Customer Success Manager

Key Technical Notes

• Extension vs. Native Agent: For Chromebooks the Chrome Extension is the standard deployment method and is pushed via Google Admin Console. For Windows and Mac, the native agent provides deeper capabilities including app blocking and screen viewing on non-Chrome browsers.

• Rostering: Securly Classroom pulls class lists and teacher-student relationships from your roster source. Roster data must be current and synced before teacher training so teachers see their correct students on the first day they log in.