Campus news portal

It reads campus, programme, year, batch and section from the student record, and department and role from the staff record. When a student moves programme or section, what they see changes with the record, not with a list someone edits by hand.

Yes. You can route every story through the communications office, or let departments with their own editors publish within their scope while institution-wide stories still need central approval. Each story records who wrote, reviewed, approved and published it.

Each channel has its own template. The portal carries the full story, the email digest a headline and short summary with a link, and the app notification a short headline. Editors can adjust any channel’s version before publishing.

For each story you can report the audience it was sent to, how many opened it, what share of the audience that was, and when. For changes such as attendance or examination rules, that is a record of what was communicated, to whom and when, which says more than an email send log.

No. The portal can run alongside them while the readership figures show departments which route reaches their audience. A department that still wants a newsletter can send it as a digest through the same editorial queue.

The institution decides which categories and priorities may send a notification, typically urgent policy changes, deadlines and closures. Within that, each person chooses what they are notified about, and every story stays on the portal. Emergency notices such as a campus closure can be set to reach everyone.

Yes. Stories can be aimed at parents by class and section and appear in the parent app, which has one login for every child in the family, next to attendance, results, fees and notices.