Tenant-isolated by design
Organization data is scoped by organization_id at every access layer. Individual Teacher data is never visible to any organization role.
Loading EtDUCATION...
Encryption in transit and at rest. Strict data isolation between organizations. Super Admin cannot directly modify organization business records beyond the RBAC model.
Talk about governanceHigh-severity risks in the product register are incorrect role access and cross-tenant leakage. Mitigation is RBAC plus tenant-scoped queries at every data-access layer.
Organization data is scoped by organization_id at every access layer. Individual Teacher data is never visible to any organization role.
RBAC at platform, organization, faculty/department, batch/class and personal levels. Affiliated teachers only see assigned batches.
Onboarding approvals, activations, security-policy changes and points adjustments are logged with actor, timestamp and outcome.
JWT or equivalent sessions across all personas. Organization Admins can configure session timeout. Temporary passwords are single-use and must be reset on first login.
Feedback is stored against teacher, submitter and batch. Tiers: EtDUCATION, teacher, organization, public. Public visibility is disabled unless separately confirmed.
Student and parent records are handled with elevated care. Specific child-data regulatory mapping is a compliance workstream to be finalized with legal stakeholders.
Discuss data isolation, points audit, session policy or organization onboarding directly with the team.