← Back to AgenticED Guardian Tenant Access is an AgenticED product
How it works

How Guardian works

Guardian proposes your workflows from the tools you already use. The district approves them, and the gate enforces them.

  1. Ask

    Guardian reads the last three months of your work history in Jira, GitHub, PagerDuty or incident.io and proposes your workflows. You review them and declare what you need.

  2. Approve

    The district approves, and the approval becomes the rows the gate reads.

  3. Keys

    The district elects a custody tier.

  4. Gate

    Every request is checked. Anything unapproved is denied.

  5. Record

    Actor, district, operation and outcome, written to a tamper-evident log.

  6. Switch

    Revoke, and access stops immediately.

The check

What every request is checked against

All five must be true at once. A person and an agent are held to the same five, and the only difference is how the first is proven.

Live

A person presents a fresh signed assertion from your identity provider, so someone who left on Friday is denied on Monday. An agent presents a registered, non-revoked credential.

Aligned

The actor is scoped to this district's tenant.

Verified

The session carries live, verified multi-factor authentication.

In role

The approval the district ratified lets this role perform this operation on this data.

Within ceiling

The request sits inside the record ceiling carried in the grant, and the key is live.

An account manager covering 40 of 800 districts reaches exactly those 40.

Request · allowed
ActorD. Ruiz · Account manager
DistrictLakeview Unified
Operationread · enrollment
Live✓ Pass
Aligned✓ Pass
Verified✓ Pass
In role✓ Pass
Within ceiling✓ Pass
Allowed · written to both records
Request · denied
Actorsvc-backup-02 · Agent
DistrictLakeview Unified
Operationexport · student_records
Live✓ Pass
Aligned✓ Pass
Verified✓ Pass
In role✕ Fail · no live assignment
Within ceilingNot reached
Denied · sent to the district’s approval queue
Fig. 1 · Two requests against the same district, decided at the moment of the request.
Key custody

Key custody tiers

Climbing the ladder changes who physically holds the key and nothing else about how Guardian works.

Tier C The district's own HSM
The key sits in hardware the district operates, reached through an external key store.
Tier B The district's own AWS account
The key sits in the district's account, reached through an assumed role.
Tier A · Default Platform managed
Zero district lift. The key sits outside the vendor in a platform-operated environment, under an enforced deny and credential separation. At this tier it does not live in the district's own account.
Export and restore

Access ends when the work ends

Export and restore are the two highest-blast-radius operations, and neither is a standing property of a job title. Both bind to a live work assignment read from your own systems. Four hours, and neither party can widen it.

Off assignment, the request is not refused silently. It goes to the district's own approval queue, naming the operation requested. A failed pull narrows rather than opens.

Setup

Setup

  1. Connect

    The MCP gateway, your current key, your workflow tool and your CRM. The four connections

  2. Review

    The review opens on what your own last ninety days of tickets show. Each proposed activity is carried with the count of tickets behind it and marked as the inference it is.

  3. Confirm

    One action proposes a connection for every district in your book. District approval runs on its own clock from there.

Authoring access rules for five thousand districts from an empty form is a project nobody finishes. Confirming what your own systems already say is a short meeting.

What does not change

  • Your SOC 2 Type II runs as it does today.
  • Penetration testing and privacy certifications are unchanged.
  • You stay accountable for your own software.
  • Guardian does not read content, inspect traffic, or judge model output.

What gets lighter

  • Key rotation.
  • Access recertification.
  • The district security review.
  • Incident scoping.
Talk to us Why now