Access & Platform
Communications
Every email the institution sends — written by the department that sends it, and provable afterwards.
What Communications does9 capabilities
- One mail configuration for the whole institution: host, port, encryption, credentials and the address replies go to — set once, used by every module
- A catalogue of every email the system can send, showing which department owns it and where its wording is edited
- Departments rewrite their own emails in their own module — subject, body and signature — with the built-in wording kept underneath and restored the moment an override is cleared
- Named department signatures (Office of Admissions, Library Circulation, Examinations) applied across that department’s correspondence
- Per-email switches: suppress a send with a recorded reason, or copy a departmental mailbox on every send of that type
- A permanent outbound log — recipient, subject, time, and the exact provider error when a send fails
- Failures are recorded before they are raised, so the message that never arrived is still on the record
- Mail health check that compares the application’s configuration against the sign-in service’s own and names the disagreement — a username with no password, a mismatched host, a from-address that will bounce
- Editing rights follow module ownership: reading the catalogue is an operations task, rewriting what applicants receive is not
