Set up Google Classroom for your school

School IT · Start here

Arrange a controlled pilot first. This is a preparation and acceptance guide, not a self-service production installer. Do not copy the demo administrator’s credentials to a school. Vero must agree a protected school authorization/signing service before rollout.

1. Agree the pilot with Vero

1. IT + Vero · Before configuration: Contact Christopher at Vero. Agree the school domain, pilot teacher, test class, synthetic students, receiving computer, devices and support owner. Done when: both parties have the same pilot scope and a private channel for setup values.
2. School Google administrator · Admin console: Confirm the teacher and test students have usable school-managed Google Workspace accounts, Classroom and Drive access, and the needed licenses or entitlements. An account appearing in Users is not proof that its services work. Do not purchase a license or enable billing as a workaround without school approval.
3. IT · Pilot class: Confirm the teacher is a teacher in the Google class and the synthetic students appear in its roster. Personal Gmail accounts are outside this school-delegation setup. Use one class per period.

2. Review the permission plan

Vero supplies the exact school-specific client identifier, approved scope list, service arrangement and revocation instructions privately. Identifiers are not passwords, but no school-specific values belong in this public guide. Never email passwords or paste credential files into the website.

Teacher access lists classes and rosters, creates assignments and checks submissions. Delegated student access uploads the PDF, attaches it and turns it in. The tested student scope pair is classroom.coursework.me and drive.file; use the complete URLs in the privately supplied, reviewed configuration. Teacher and signing permissions are separate. IT must review the complete plan, not authorize only these two shorthand labels.

Domain-wide delegation is powerful: Google grants it across the domain within the approved scopes. Vero’s course/student allowlist is an additional application check, not a Google-enforced restriction to those students. Google’s delegation guidance recommends avoiding delegation unless necessary.

3. Authorize the agreed school connection

1. Vero operator + IT · Approved service: Configure the protected service identity and enable the Classroom and Drive APIs in the assignment-creating Google project. Keyless signing also needs the IAM Service Account Credentials API and narrowly scoped signing access. Keep privileged signing authority out of Writer, browsers and ordinary Companion installers. Confirm the arrangement and costs before enabling services.
2. Google Workspace super administrator · Admin console: Open Security → Access and data control → API controls → Manage Domain Wide Delegation → Add new. Enter only the numeric client ID and exact scopes supplied for your school. Review the request, then choose Authorize. A second administrator may need to approve it under school policy.
3. IT + Vero · Verification: Inspect the saved client and scopes. Allow for propagation; Google notes changes can take up to 24 hours. Verify approved teacher and synthetic-student access without a student login. If access fails, check account services, licenses and the exact grant; do not broaden scopes blindly.

Follow Google’s administrator instructions for the current controls and revocation procedure. This guide intentionally contains no filled authorization screenshot or live credentials.

4. Prepare Companion and prove delivery

1. IT + Vero · Teacher computer: Install/update Companion without deleting received work. Configure the approved Vero teacher, school, Google classes and student identity mapping privately. Verify Bluetooth and browser access to the local Companion. Keep the local service private to this computer.
2. Teacher + IT · Vero portal: Follow Connect and check your class, then create a synthetic assignment using the classroom guide. Confirm the selected class and roster.
3. Teacher + IT · Real Vero device: Join, approve the correct student, write and finish. Confirm the device receipt, then Sent to Google Classroom. Open the teacher’s Google assignment and inspect the correct student’s PDF and turned-in status.
4. IT + Vero · Acceptance: Test restart/retry, network loss and recovery, a wrong account or class, and permission revocation/recovery. Confirm duplicate retries do not create duplicate submissions. Record results, retention/backup arrangements and support ownership. These school-environment checks are required; demo success does not replace them.

5. Hand over to the teacher

Give the teacher the configured computer, approved class names, connection and classroom guides, and the support contact. Do not give them service credentials. Confirm who can revoke authorization if the pilot ends. Teachers are ready only after the synthetic PDF is visible to the correct Google teacher.