Access by approved implementation.

Security

Designed around minimum-necessary visibility.

AnchorGrey Records keeps program operations focused on status, readiness, and review workflow while treating sensitive documents as a controlled records lane rather than routine program-view content.

Access is provisioned through approved institutional implementation.

AnchorGrey Workspace

Director workspace

Spring 2026 cohort

Tenant provisioned
42Learners
24Complete
8Action needed
Reviewer workflow5
Program review11
Expiration watch7

Learner checklist

TB documentation
MMR record
Program form

Reviewer queue

Correction needed
Escalation

Status first

Programs get the readiness signal.

Director views are designed around requirement status, missing counts, learner action needs, review state, and expiration risk.

Role-based visibility

Sensitive documents stay in controlled lanes.

Reviewer paths and program dashboards are separated so routine program views do not become raw-document workspaces by default.

Implementation control

Pilot readiness is a gate, not a slogan.

Each approved implementation should define access, consent, retention, audit, support, and records workflows before rollout.

Architecture direction

Built for a future secure records architecture.

AnchorGrey's product architecture is planned around identity, metadata, encrypted object storage, audit logs, reviewer queues, and status-only program reporting.

View architecture overview

Core implementation controls

  • Signed Google BAA
  • HIPAA Included Functionality confirmed
  • Legal review of HIPAA/FERPA model
  • Consent or authorization workflow reviewed
  • Access-control matrix reviewed
  • Retention policy reviewed
  • Audit logging enabled
  • Backup and restore tested

No fake badges

Confident, but honest.

AnchorGrey does not need invented compliance badges to sell the product. The credible posture is stronger: minimum-necessary reporting, controlled implementation, explicit access design, and program-retained final authority.