Configuration Hub (Critical — SMS, WhatsApp, Email, Notifications)
Purpose
The Configuration area is where the school connects the system to the outside world: email server, SMS gateway, WhatsApp Business API, notification toggles, school hours, academic calendar dates, and display currency (see Module B9).
Who uses it
Super Admin, Head Officer, School Admin.
Super Admin only (system-wide SMS/WhatsApp defaults): must switch to Global View in the top header first — see B5.0 below.
Depends on
Institution selected in header (or Global View for platform-wide communication defaults).
B5.0 System Default SMS & WhatsApp (Super Admin — Global View only)
Purpose: Set the platform-wide SMS and WhatsApp providers and API credentials. These replace static .env values (SMS_DRIVER, MOBISHASTRA_*, etc.) for every school that chooses System Default (Digitex Credits).
Who uses it: Super Admin only.
Important — you must use Global View:
- Log in at https://e-digitex.com/login
- Click the building icon (institution switcher) in the top-right header
- Select Global View — the header should show "Global View", not a school name
- Menu → Configuration → ID Sender SMS tab
- Confirm the blue Global Mode badge appears on the Communication Setup card
If you open Configuration while a school (e.g. Green Valley) is selected, you will only edit that school's settings — not the system defaults. A yellow warning appears reminding you to switch to Global View.
Step-by-step — configure system defaults:
- Under Provider Availability Control, tick which providers schools may use individually (e.g. Mobishastra, Infobip, Twilio, SignalWire for SMS; Meta, Infobip, Twilio for WhatsApp)
- Set System Default SMS Provider — e.g. Mobishastra
- Set System Default WhatsApp Provider — e.g. Meta
- Open the API Credentials tabs and enter platform credentials (example Mobishastra):
| Field | Example value |
|---|---|
| Username (Profile ID) | INTEGRALE |
| Password | (your Mobishastra password) |
| Sender ID | ARCHIDIOKIN |
- Click Save Changes
- Use Configuration → Test Notifications to send a test SMS/WhatsApp
How schools use this:
- Each school can set Active SMS Provider = System Default (Digitex Credits) — messages use your Global View credentials and deduct SMS credits from that school
- Or a school can pick its own provider (e.g. Twilio) and enter its own API keys — no credit deduction for that channel
Common questions:
Q: I saved Mobishastra in .env but the UI still shows another provider.
A: Global View settings in the database override .env. Change them in Global View, or remove the global DB rows to fall back to .env.
Q: Can I configure this without Global View?
A: No. System defaults are stored with no institution (Global View context). Always switch via the header building icon first.
B5.1 SMTP (Email) — Example Setup
Purpose: Send invoice emails, password resets, and email notifications.
Steps:
- Configuration → SMTP tab
- Example values (using Gmail-style SMTP — your IT team provides real ones):
| Field | Example value |
|---|---|
| Mail Host | smtp.gmail.com |
| Port | 587 |
| Encryption | TLS |
| Username | notifications@gvis.edu.ci |
| Password | (app password from Google) |
| From Address | notifications@gvis.edu.ci |
| From Name | Green Valley School |
- Click Save, then Send Test Email to
secretary@gvis.edu.ci. - If test succeeds, enable Email column for events like *Invoice Created* under Notification Settings.
Common question: *Emails go to spam.* — Ask IT to set SPF/DKIM records for your domain.
B5.2 SMS Provider — Example Setup (School level)
Purpose: Send fee reminders, OTP codes, arrival SMS to parents.
Note for Super Admin: Platform-wide defaults are configured in B5.0 (Global View). This section is for a single school's own provider or for choosing System Default (Digitex Credits).
Supported providers (examples): Mobishastra, Infobip, Twilio, SignalWire.
Steps:
- Select the school in the header (or stay in Global View only for B5.0)
- Configuration → SMS / WhatsApp tab
- Choose Active SMS Provider:
- System Default (Digitex Credits) — uses Super Admin global config (B5.0); credits deducted
- Twilio (or other) — school uses its own API keys; no credit deduction
- If using your own provider, fill credentials (example for Twilio):
| Field | Example value |
|---|---|
| Account SID | ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| Auth Token | (secret — paste once, stored encrypted) |
| From Number | +15551234567 |
- Sender ID (if provider uses alphanumeric):
GVIS - Save → Send Test SMS to
+2250712345678 - Message should arrive: *"Test message from E-Digitex (14:32:05)"*
Mobishastra example:
| Field | Example |
|---|---|
| User | gvis_sms_user |
| Password | (secret) |
| Sender ID | GVIS |
Credits: SMS costs credits. Super Admin recharges under Configuration → Recharging.
B5.3 WhatsApp Provider — Example Setup
Purpose: Parents receive homework alerts, payment confirmations, pickup messages on WhatsApp.
Common providers: Meta Cloud API, Infobip, Twilio.
Meta (Facebook) WhatsApp example:
| Field | Example value |
|---|---|
| Phone Number ID | 123456789012345 |
| Business Account ID | 987654321098765 |
| Access Token | EAAxx... (long token from Meta Developer Console) |
Twilio WhatsApp example:
| Field | Example |
|---|---|
| WhatsApp From | whatsapp:+14155238886 |
Steps:
- Select WhatsApp Provider = Meta (or Twilio)
- Paste credentials → Save
- Test tab → send test WhatsApp to parent phone
- Under Notification Settings, enable WhatsApp for Payment Received, Student Arrival, etc.
Webhook for chatbot: Point Meta/Twilio webhook to:
https://e-digitex.com/api/v1/chatbot/webhook/meta (or twilio)
B5.4 Notification Preferences (SMS / WhatsApp / Email / In-App Bell)
Purpose: Decide which events send which type of message.
Steps:
- Configuration → Notification Settings
- You see a table of events, e.g.:
| Event | SMS | In-App (Bell) | ||
|---|---|---|---|---|
| Payment Received | ☑ | ☑ | ☐ | ☑ |
| Invoice Created | ☐ | ☑ | ☑ | ☑ |
| Student Arrival (RFID) | ☑ | ☑ | ☐ | ☐ |
| Exam Results Published | ☐ | ☑ | ☐ | ☑ |
- Check boxes → Save Changes
Example policy at Green Valley:
- All fee events → WhatsApp ON (parents prefer WhatsApp)
- Staff leave requests → In-App bell ON for admins only
- Marketing bulk SMS → OFF (use Reminders module manually instead)
Default behavior: If you never saved preferences, in-app bell is ON by default for most events; SMS/WhatsApp are OFF until you enable them (to avoid accidental charges).
B5.5 School Year and Gate Timings
Purpose: Tell the system when school starts, when a student is "late", and how long between check-in and check-out at RFID gates.
| Setting | Example | Meaning |
|---|---|---|
| Academic Start Date | 2025-09-01 | First day of year |
| Academic End Date | 2026-07-15 | Last day |
| School Start Time | 08:00 | Classes begin |
| School End Time | 15:00 | Classes end |
| Late Margin | 15 minutes | Arrival before 08:15 = on time |
| Double Tap Wait | 15 minutes | Must wait 15 min between IN and OUT scan |
Depends on: Used by Student Attendance (hardware and manual) and reports.
B5.6 SMS Templates
Purpose: Edit the wording of automatic messages. Templates use tags like $StudentName, $Amount, $SchoolName.
Example template — Payment Received:
Dear Parent, payment of $Amount for $StudentName has been received.
Remaining Balance: $Balance. Thank you, $SchoolName.Steps: Configuration → SMS Templates → select event → edit body → Save.
B5.7 Enabled Modules (Super Admin)
Purpose: Turn entire feature areas on/off per school subscription.
Example: Sunrise Primary package includes Students + Invoices but NOT Elections. The Elections menu will not appear for that school.
Still need help?
Ask on the forum