Req 2.96: The Supplier shall assist DepEd in defining govern...

⚙️ Technical Demonstration

IMTLazarus completely satisfies this requirement by providing a multi-tenant, Role-Based Access Control (RBAC) architecture that maps directly onto DepEd’s hierarchical organizational structure. The platform enforces strict isolation and separation of duties, ensuring that administrative privileges are granted contextually based on the four requested operational scopes:

Reporting Administrators (All Levels): Provisioned with read-only or specialized analytical access to generate fleet data metrics. They extract compliance logs, enrollment audits, inventory snapshots, and usage patterns for governance reporting without possessing the rights to alter active security policies.

Policy Approvers (Central / Regional Level): Granted high-level authorization to define, refine, and lock global configuration blueprints, baseline web filtering schemas, and mandatory systemic restrictions. They hold exclusive rights to approve overrides or modify top-tier security standards.

Configuration Managers (Division Level): Responsible for the day-to-day lifecycle maintenance of the fleet. They oversee device enrollments, assign specific structural profiles to Organizational Units (OUs), map timetables, and execute remote commands (lock, wipe, or troubleshoot) across their division.

Safeguarding Reviewers (School / Division Level): Focused strictly on student protection and digital wellness. They maintain dedicated access to the Logs & Activity ecosystems, monitoring real-time keyword alerts, blocked web attempts, category exceptions, and YouTube dashboard telemetry to flag or mitigate safety concerns.