Tenet goes from decision to deployed in under a day, using tools the district already owns, with no new infrastructure, no network changes, and no agent installers. This is the guide for the IT-director conversation.
Tenet is delivered as a managed Chrome extension. A district pushes it from the Google Admin Console the same way it pushes any other approved extension, and it lands on every managed Chromebook in minutes. Students cannot disable, uninstall, or bypass it, because it is installed by district policy rather than by the user.
Google Admin Console, then Devices, Chrome, Apps and extensions, then Force install. This is the same flow IT already uses for other extensions, and it takes about ten minutes.
The admin sets the district-wide rules and approved-AI list in the dashboard, roughly 30 to 60 minutes. Teachers add their own class rules later (Pro).
Pro features that need a roster import it via CSV today, with ClassLink and Clever integration shipping fall 2026. Basic needs no roster at all.
A pre-cleared Student Data Privacy Consortium template makes the data privacy agreement fast, typically under two weeks, and it runs in parallel with everything else.
Live the same business day. Force-install is minutes, rule setup is under an hour.
Two to three days, mostly to import the roster and let teachers set class rules.
Force-install also works on managed Windows via Edge policy, where applicable.
| Common rollout task | With Tenet |
|---|---|
| Stand up servers or infrastructure | None. Our backend is hosted. |
| Network or firewall changes | None. |
| SSL certificates or proxy setup | None. There is no proxy. |
| Agent or software installers on each device | None. It is a managed extension. |
| Replace the existing web filter | No. Tenet pairs alongside it. |
| Identity and login plumbing | Uses the district's existing Google Workspace. |
A single setting that turns Tenet's enforcement off district-wide, instantly, if something needs to be paused. IT is never stuck.
Sanitized, categorical analytics that the district owns and can route to its own storage, Google Sheets, S3, GCS, or a webhook. Student names are hashed or redacted before capture.
The multi-tenant backend isolates every district at the database level, so one district can never see another's data.
Tenet is built to coexist with the major web filters, including a compatibility mode for districts running Securly.
The whole rollout is a few hours of hands-on time, with no infrastructure, no network changes, and an emergency off switch. This is the easiest yes you will give all year.
The district can move now, this week, rather than waiting on a multi-month procurement and integration project.
A building playbook for the first week, a short weekly pulse, and clear signals when a classroom has not finished setup.