We'll email a verification code to your account's address. Entering it removes the lost authenticator app so you can set up a new one.
Your district requires a code from an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password and others) when you sign in.
District-wide screen time at a glance
By day
Total minutes, local time
Viewing individual student activity is recorded in the audit log. Select a student to open their detail.
Select a site to see page titles
Students who used each product in the selected range, matched by the product's domains. Select a product for trends and details.
Websites students used in this range that are not matched to any product. Add the ones that matter so they can be reviewed and tracked.
Annual cost of every product that isn't denied, grouped by its budget owner. Budget owners that match a school on the Schools tab are sites. License use follows the date range above.
Select a product to open it.
Viewing individual student activity is recorded in the audit log.
Schools in the district and their principals. Devices and assets are matched to a school by the school name in their Google Admin policy or asset record.
School names reported by devices or used on assets that don't match a school above. Add the real ones; fix typos in Google Admin or the asset record.
Select an asset to see its details and assignment history. Viewing student assignments is recorded in the audit log.
Approved tools can be used with students now. For anything not approved or not listed, submit a request.
Requests you've submitted and the district's response. You can withdraw a request until it's decided.
Ask the district to approve a new software, app or website to use with your students. Track it and see the decision under My Requests. Check the software catalog first: approved tools can be used now.
Teacher requests to approve new platforms. Approving can add the platform to the software catalog as approved.
Applies to every enrolled device. Devices pick up changes the next time they check in.
How long student data is kept and what is collected. Older data is purged automatically every 6 hours.
Outgoing email for software request notifications and password recovery. Email is only sent encrypted (TLS or STARTTLS) and the mail server's certificate is always verified.
Send audit events and server logs to your SIEM or log server in standard syslog format. Logs are only sent encrypted, over TLS (RFC 5425), and the log server's certificate is always verified.
Checked categories count as Screen Use (educational value). Everything still counts toward Screen Time. Changes apply to all past and future data immediately.
Select a site to fill it into the form above.
Read-only tokens for BI tools. Use Authorization: Bearer <token> on /api/reports/<name> or /api/reports/<name>.csv.
Tokens read aggregate reports only (schools, grades, sites, software). Student-level reports (students, page titles, devices, assets) need the checkbox and are a disclosure of education records to the tool using the token: only enable it for a tool covered by your data agreements.
When a parent or eligible student asks to see their records (FERPA allows 45 days) or a parent asks to review their child's data (COPPA), look the student up here. Every export and access-history view is recorded in the audit log.
From the audit log. Named this student entries are certain; Device on loan means someone opened a device record while the student had it; List that may include means a list report whose dates, school and grade covered the student's activity. API tokens are outside tools, so their access is a disclosure.
Permanently removes all usage records for one account (records requests, withdrawals).
Usage is deleted. Device loans and audit entries are kept for accountability but no longer name the student.
For the end of a contract or a district-wide deletion request. Deletes all usage data and returned device loans, removes students from active loans, devices and the audit log's details. Users, settings, schools, assets and the software catalog are kept. This cannot be undone.
People who can sign in to ScreenWise. Permissions come from each user's role plus the roles of their groups. Changes apply immediately, even to users who are signed in.
Give a set of people the same access at once, for example a school's front office or the curriculum team. Members get the group's role on top of their own.
A role is a named set of permissions. Built-in roles can't be deleted, and Administrator always has every permission.
What each role can do.
Sign-ins, views of student data, and every change to users, access and settings.