Roles
Students, teachers, school leaders, IT staff and administrators can require different model access, tools, knowledge collections and operational permissions.
ZYK Control
Schools need an AI control plane, not a collection of individual settings.
ZYK Control is the proposed institutional governance and administration layer for identity, permissions, model access, audit, consent, retention, filtering, review and operational visibility.
Identity & policy
Define who can use what — and under which rules.
Model permissions
Institutions can define which approved models or capabilities are available to which roles and contexts.
Usage rules
Quotas, feature availability, age-appropriate restrictions and school policies can be applied centrally rather than configured by every user.
Approval workflows
Selected generated materials or sensitive workflows can require teacher or administrative review before use or publication.
Governance records
Controls should be inspectable, not invisible.
Audit logs
Record relevant access and system events to support troubleshooting, governance review and incident investigation.
Consent state
Where consent is an appropriate legal basis or institutional requirement, workflows can track status and associated records.
Retention & deletion
Policies can define how long different classes of information are kept and how approved deletion workflows operate.
Incident review
Administrators need a structured way to investigate problematic outputs, policy breaches or suspicious access without relying on screenshots and memory.
Content & model governance
Safety controls belong above individual applications.
Filtering
Text, image and other content controls can be configured as institutional policy rather than left to each teacher or student.
Labelling
AI-generated-content labelling and watermarking settings can be applied where appropriate to the use case and applicable rules.
Model catalogue
Schools can maintain an approved catalogue of models, versions and intended use cases rather than allowing uncontrolled model switching.
Sandbox boundary
Experimental models and workflows can be separated from production services so testing does not automatically become institutional deployment.
Multi-school direction
Control can scale from one school to a group or region.
A future group-level control plane could define common governance baselines while allowing schools to retain campus-specific users, knowledge, schedules and educational workflows.
Group baseline
Approved model list, minimum controls, documentation requirements and common service standards.
Campus autonomy
Local curriculum, permissions and operational settings can remain within defined school-level boundaries.
Central visibility
Group or bureau administrators may need aggregated health, policy and utilisation views without exposing inappropriate school-level personal data.
ZYK Control is a content-v2 strategic product concept. It organises governance features already present across the ZYK business plan, but its exact implemented feature set must be validated before commercial publication.