The install conversation is where most K-12 deals stall. Tenet's is three steps and an afternoon: add the extension, paste a short config in Google Admin, and (for Pro) upload a simple roster. This guide shows you how to say that with confidence and get the details right.
Districts have been burned. They expect new software to mean agents on every device, network changes, certificates, and a multi-month IT project. So when an IT director hears "another tool," they brace for work. Tenet flips that expectation, and the ease of install is one of your strongest closing tools. Lead with it.
Steps 1 and 2 are all Basic needs and take minutes. Step 3 is Pro, and even then it is a single CSV.
Tenet is a Chrome extension, published on the Chrome Web Store. IT does not push an installer to each laptop. Instead they force-install it from the Google Admin Console:
In the same Google Admin screen, the extension has a "policy" field. The district pastes a few lines of JSON that tell the extension which district it belongs to and how to reach the Tenet backend. Tenet hands IT the exact snippet. It looks like this:
That is it. The config sets the district identity, the backend address, and the Google sign-in client used for verified login. IT pastes it once, and every device picks it up automatically.
To turn on classroom-level features (per-teacher rules, roster-aware privacy, class views), Pro takes a simple roster as a CSV. No integration project, just a file. Live ClassLink and Clever sync is on the way for fall 2026. Basic does not need this at all.
This is the detail reps most often get wrong. Be precise, because it shapes what data the district has to share.
Name these out loud. Each one is a project the IT director was bracing for and will not have to run.
| What they expect | With Tenet |
|---|---|
| Stand up servers or infrastructure | None. The backend is hosted. |
| Network or firewall changes | None. |
| SSL certificates or a proxy | None. There is no proxy. |
| Install software on each device | None. It is a managed extension. |
| A new login system | Uses the district's existing Google Workspace. |
| Replace the current web filter | No. Tenet runs alongside it. |
Tenet keeps prompts on the device and only sends sanitized, aggregate analytics. Districts choose where that data lands, and standing it up is quick.
The fastest path. A district can stand up a Google Apps Script endpoint in about five minutes and have analytics flowing into their own Google Workspace, no extra vendors.
For larger districts, Tenet writes to Amazon S3, Google Cloud Storage, or Azure Blob Storage. Point it at the bucket your data team already runs.
If your team is technically proficient, you have everything you need to stand it up yourselves. If not, we are happy to set the whole thing up for a one-time stand-up fee.
Keep it concrete and short. The whole point is to make the install feel small.
"Here is literally all you do. You force-install our extension from the same Google Admin screen you already use for other extensions. You paste a short config we give you, three lines, that tells it your district. That is Basic, live today. If you go Pro, you upload one roster CSV to turn on the per-teacher classroom controls. No servers, no network changes, nothing on the student laptops. If you ever want to pause it, there is a single off switch."
Then hand them the one-page IT rollout guide and offer to be on the call when they push it. The deploy is usually shorter than the conversation about it.
Same business day. Force-install plus the config, and you are live.
2 to 3 days, mostly to upload the roster and let teachers set their class rules.
The data privacy agreement, on a pre-cleared SDPC template, is usually under two weeks and runs in parallel.