Custom modifications to fit your exact safeguarding needs.
Child Protect Platform can be adapted to match the real operating model of your school, tenant, safeguarding team, reporting process, evidence workflow, integrations, and governance requirements.
Quick answer
Can Child Protect be customized?
Yes. Child Protect can be adapted for school-specific workflows, reports, Google Workspace use, CRM integration, user roles, and multi-school operational needs.
Flexible where your organization needs flexibility. Controlled where safeguarding requires control.
Every school group works differently. The platform can support tailored workflows and presentation while preserving the core principles that matter: least privilege, auditability, evidence preservation, tenant/school separation, and secure operation.
Desktop, tablet, and mobile ready.
Child Protect Platform is designed for modern web browsers, giving administrators, safeguarding teams, and school users responsive access from desktop, tablet, and mobile devices without requiring a separate app.
What can be customized?
Common customization areas for schools, multi-school groups, safeguarding organizations, and Thailand-focused deployments.
Workflow stages
Adapt intake, review, triage, assignment, escalation, closure, and retention steps to match your safeguarding policy and operational structure.
Forms and required fields
Adjust report forms, dropdowns, required information, school/site details, case categories, and supporting notes so staff capture the right information.
Roles and permissions
Configure access models for platform administrators, tenant administrators, school administrators, safeguarding leads, investigators, reporters, and auditors.
CRM and Google Workspace integration
Discuss integrations with your existing school CRM, Google Workspace, directory tools, email workflows, or approved administrative systems so safeguarding work fits your current environment.
Direct feature requests
Capture organization-specific requests such as custom dashboards, approval paths, notifications, data exports, onboarding steps, reports, and implementation support.
Tenant and school setup
Support single-school, multi-school, multi-campus, foundation, education group, NGO, or service-provider operating models with appropriate separation.
Multi-school modelEvidence handling
Align evidence upload, scanning, encryption, access control, review, audit logging, backup, and recovery workflows with organizational practice.
Evidence preservationLanguage and localization
Adjust English/Thai wording, labels, navigation, help text, and user-facing instructions so staff understand exactly what to do.
Thailand alignmentReports and dashboards
Shape dashboards, status views, audit exports, leadership summaries, and operational reporting around the information your team needs most.
Case managementExisting systems and integrations
Plan safe integration points with school CRM platforms, Google Workspace accounts, email notifications, user directories, approved exports, and other systems your school already relies on.
Discuss integrationsCustom requests
Review direct requests from leadership, safeguarding teams, IT, school administrators, and partners so the platform can support real operational needs without weakening security controls.
Share requirementsExamples of fit-to-need changes
Different schools can use consistent controls while still matching local terminology, timezone, language, and reporting expectations.
Teams can separate reporting, review, investigation, administration, and audit responsibilities without exposing unnecessary information.
Evidence handling can be presented clearly to users while preserving encrypted storage, controlled access, and reviewable activity history.
Where appropriate, the platform can be planned around existing CRM, Google Workspace, email, user-management, reporting, and administrative workflows.
What should stay standardized?
Security controls, audit logging, evidence preservation, tenant/school isolation, responsible data handling, and hardened hosting should remain consistent. Customization should improve fit and adoption without weakening the safeguards that protect sensitive information.
Need a version that fits your organization?
Tell us about your school structure, reporting workflow, CRM or Google Workspace environment, integration needs, language needs, evidence requirements, direct feature requests, and user roles. We can discuss the safest way to adapt the platform while keeping the security model strong.