IT administrators · School staff

IT admin & enterprise

Self-paced · updated with each release

Audience: School IT admin, operations head
Duration: ~2 hours
Prerequisites: Getting started guide


Learning objectives

  • Manage users, roles, and teams
  • Configure integrations
  • Enable MFA and enterprise settings
  • Use trust center for compliance exports

1. Users & roles

Route Purpose
/school-panel/users Invite staff, assign roles
/school-panel/roles Permission matrix (read-only for custom roles)
/school-panel/teams Admission teams for lead routing

Roles: school_admin, counselor, finance, etc. — assign them under /school-panel/roles. For admissions workflows, share the Counselor guide; for messaging connectors, see the Communications playbook.


2. Campuses & governance

Route: /school-panel/campuses, /school-panel/settings/governance

Multi-campus scope via X-Campus-Id. Franchise policies for groups.


3. Integrations

Route: /school-panel/integrations — see Integrations marketplace for install and health checks.

Integration Use
WhatsApp Omnichannel messaging
Telephony Twilio / MCube
Webhooks Outbound events to your systems

Route: /school-panel/webhooks — subscribe to lead/payment events.


4. Enterprise settings (Wave 11 + i18n)

Route: /school-panel/settings/enterprise

Feature Action
Branding Logo and colors for comms
MFA Require TOTP for admin users
UDISE Fill profile → export for gov reporting
Locale Default language — English, Hindi, or Gujarati (User.preferredLocale)

Staff can also switch language from the LocaleSwitcher in the ERP header. CRM and ERP page titles follow the selected locale; many page bodies are still English while i18n rollout continues — see SKOLZO_CAPABILITY_MATRIX.md.

MFA setup: user scans QR in profile → login challenges on next sign-in.


5. Trust center

Route: /school-panel/trust-center

  • Audit log export
  • Data retention settings
  • Consent records

6. API keys & usage

Route: /school-panel/api-keys, /school-panel/usage

For custom integrations — rotate keys periodically. Skolzo subscription billing and seat meters are covered in Plans, billing & usage. Approval queues for sensitive actions: Approvals & workflows.


Practice exercise

  1. Invite a test user with counselor role only.
  2. Connect mock telephony integration in demo.
  3. Enable MFA on your account and verify login challenge.
  4. Export audit log sample from trust center.

FAQ

Parent logged into CRM? — Parent accounts must use skolzo.com; block from staff apps is intentional.

Troubleshooting

Integration webhook failing — Check API keys in /school-panel/integrations and that your server allows Skolzo callback URLs.

Go deeper: Counselor integrations section · Getting started