Tenet Supported AI Products: Capability and Validation Matrix

Current status: Last reviewed August 11, 2026. Validation register updated September 8, 2026: 35 local automated checks passed on Tenet 1.1.127 source. Signed-in vendor control results remain unverified in this register.

Tenet Edge currently supports ChatGPT, Claude, Gemini, Microsoft Copilot web and Bing chat, Grok, MagicSchool MagicStudent and Raina, SchoolAI student Dot spaces, and Brisk Boost on district-managed Chrome devices. Feature availability varies by product surface, content type, district configuration, and rollout scope.

This is a surface-level compatibility statement, not a claim that every feature inside each vendor product behaves the same way. A district should identify the exact product URL, account type, user role, content type, and required control before treating a workflow as covered.

Last reviewed August 11, 2026. The vendor references on this page confirm product names and web experiences. Tenet compatibility status is based on TrueMadeAI’s current managed Chrome implementation and rollout scope.

A separate layer for unapproved AI interfaces

The supported-product matrix below lists web experiences within Tenet’s declared governance scope. The versioned validation register above separates that scope from evidence for each control. Tenet Basic and Tenet District also include an optional blocking layer for AI chat and writing interfaces that the district has not approved.

Approved products, district allowlists, and bypass domains remain authoritative. Detection happens on the managed Chrome device. A detection does not convert that product into a deeply supported surface and does not imply that Tenet can apply prompt policy, DLP, or response controls inside it.

Grammarly is a current example of why the distinction matters. Its August 2025 product announcement describes an AI-native writing surface with AI Chat and specialized agents. For a validated Grammarly web surface, Tenet can use a known interface signature to block the unapproved AI panel rather than blocking the entire surrounding writing application. Districts should confirm the exact route and behavior during rollout because vendor interfaces change.

Current supported-product capability matrix

The table distinguishes the supported web experience from adjacent features that are not automatically included.

Product names are trademarks of their respective owners. Listing a product does not state or imply a vendor partnership, endorsement, or certification.

What the capability labels mean

Managed access policy

A district can include the named product in its approved AI policy and apply managed-device access decisions under the configured Tenet rules. Access eligibility is different from deep control inside every feature of the product.

Plain-text prompt checks

On a validated direct-chat composer, Tenet can evaluate supported plain-text student input against the enabled district rules before the message is submitted. Available checks depend on account role, tier, policy settings, and the active product surface.

District guidance

On supported direct-chat paths, Tenet can apply district guidance to the conversation flow. Tenet Basic uses one district-wide baseline. Tenet District can resolve additional grade, roster, class, teacher, period, and schedule context.

On-device DLP

Tenet can evaluate supported plain-text paths for configured sensitive-data patterns on the managed device. Tenet District can add roster-aware context where supported. This does not mean every file, image, attachment, generated response, or vendor-side feature receives the same inspection.

Basic and District use the same product register

The difference between Tenet Basic and Tenet District is policy resolution, not a different list of vendor products.

Both tiers include DLP on supported and configured paths, plus optional blocking for detected unapproved AI chat and writing interfaces on managed Chrome. Tenet District adds roster-aware context and pseudonymization where supported. Neither tier turns a detected or unsupported vendor feature into a deeply supported one.

Both tiers can send supported general analytics to configured district-controlled destinations through bring-your-own-storage (BYOS) exports. Incident evidence is a separate data class and may preserve conversation text and identifying context for defined safety or compliance events when active for a deployment. Routine prompt and response bodies are not routed through the TrueMadeAI backend. See the privacy notice for the complete hosted-data, provider, analytics, evidence, and alert boundaries.

What is outside this matrix

This page does not claim current Tenet Edge coverage for:

• native mobile or desktop applications;
• unmanaged browsers or personal devices outside the district deployment;
• deep governance of AI assistants embedded inside productivity suites, learning platforms, or operating systems unless that exact surface is named; the optional blocking layer may still detect and stop an unapproved interface;
• every file upload, attachment, image, voice, video, canvas, connector, plugin, custom assistant, or agent workflow;
• every model response or vendor-generated action;
• arbitrary model APIs used by district applications.

Direct-use governance and backend AI governance are separate technical planes. Tenet Edge applies policy on the supported managed-device experiences listed here. Tenet Gateway is a founding-district program for approved backend AI operations inside district applications.

District rollout verification checklist

Before a district calls a workflow supported, verify:

1. Device: The user is on a district-managed Chrome device in the intended deployment group.
2. Surface: The exact hostname and product route match the supported web experience.
3. Identity: The district knows whether the user is a student, educator, or staff member and which account is active.
4. Tier context: The expected district, grade, roster, class, teacher, period, or schedule rule resolves correctly.
5. Content type: Plain text, pasted content, file, image, voice, or another format is tested separately.
6. Decision: Allow, guide, warn, redact, or stop behavior matches the district configuration.
7. Vendor change: The workflow is retested after a material vendor interface, account, or feature update.

For the broader operating model, use the K-12 AI governance guide, the AI application register template, and the AI tool vetting template.

Frequently asked questions

Which AI products does Tenet Edge currently support?

Tenet Edge currently supports ChatGPT, Claude, Gemini, Microsoft Copilot web and Bing chat, Grok, MagicSchool MagicStudent and Raina, SchoolAI student Dot spaces, and Brisk Boost on district-managed Chrome devices. Feature availability varies by product surface, content type, district configuration, and rollout scope.

Does supported mean every feature inside each AI product is governed?

No. Support applies to the named web surfaces and validated interaction paths. It does not automatically include every file flow, image tool, voice mode, custom assistant, connector, native application, embedded assistant, or newly released product feature.

Can Tenet block an unapproved AI chatbot that is not in the supported-product matrix?

Yes, on district-managed Chrome when the district enables the optional control and the interface matches a known signature or the local multi-signal detection threshold. Tenet can block the detected AI chat or writing interface while district allowlists and bypasses remain authoritative. Coverage depends on the current web surface and vendor changes.

Does detecting an AI interface mean Tenet deeply supports that product?

No. Detection and blocking are separate from deep governed support. A detected interface can be stopped without claiming prompt controls, DLP, policy guidance, or response monitoring inside that product.

Do Tenet Basic and Tenet District support different AI products?

The named product coverage is shared across Tenet Edge. Tenet Basic applies one district-wide baseline. Tenet District adds grade, roster, class, teacher, period, and schedule context where the selected capability supports it.

Does Tenet Edge support mobile applications or unmanaged browsers?

No. The current Tenet Edge scope is district-managed Chrome devices. A vendor’s mobile app, desktop app, browser sidebar, or unmanaged browser session is not included merely because its web chat is listed.

Does Tenet Edge govern AI used inside district applications through an API?

No. Tenet Edge governs direct use on supported managed-device surfaces. Tenet Gateway is a separate founding-district program for approved backend AI operations inside district applications.

Does Tenet provide DLP for every prompt, file, and model response on every supported product?

No. Plain-text prompt DLP is available on supported paths when configured. File, image, attachment, and response-level behavior varies by product surface and content type and must be validated for the district’s intended workflow.

Product references

These vendor sources document the named product experiences. They do not describe or certify Tenet compatibility.

• What is ChatGPT: FAQ, OpenAI
• Claude access interfaces, Anthropic
• Use Gemini Apps, Google
• Microsoft Copilot and Copilot in Microsoft 365, Microsoft
• Welcome to Grok, xAI
• AI tools for K-12 students, MagicSchool
• Getting Started with Spaces, SchoolAI
• How students use a Boost Activity, Brisk Teaching
• Grammarly launches AI agents and an AI-native writing surface, Grammarly

For procurement, account eligibility, student privacy, retention, training use, and contractual terms, districts should review the vendor’s current documentation and agreement for the selected account and deployment.