platform
Trust & Governance
Authority, evidence and privacy by design.
01
Permission-scoped collaboration
- Proposed RBAC and ABAC combine role, tenant, institution, programme, assignment and record attributes.
- Shared multi-party programmes require explicit permissions; funding participation does not grant access to every learner record.
- Delegations, segregation of duties and periodic access reviews form part of the intended control model.
02
Personal information and minors
- POPIA-aligned design intentions include lawful purpose, consent where applicable, minimisation, retention and data-subject requests.
- Guardian links must be authorised; child support and sensitive records should be restricted to appropriate roles.
- AI prompts and outputs should minimise PII, respect tenant policy and record the evidence used.
03
Verification before claims
- Encryption, isolation, audit logging, backups and resilience are intended controls, not independently verified operational certifications.
- Security review, permission testing, deployment evidence and recovery exercises are required before operational assurances.
- Confirm retention, deletion, escalation and breach-response responsibilities during discovery.
Discuss a pilot or book a demo
Tell us about your schools, district or programme. We’ll show how SkillsCortex could connect your workflows — and agree what a scoped pilot would prove.