Every office,
in sync
Admissions, records, results and finance on one platform, so the whole university moves together. The demo is a live, working copy: sign in and take it for a spin.
- 6modules running in the demo
- 15staff roles, each with its own view
- 3students at different stages
- 3applicants mid-admission
What universities brought to us
Six problems, one system that answers each of them
| Area | Before | With University System Suite |
|---|---|---|
| 01Access |
Before |
Self-service portal for students and staff, any time |
| 02Records |
Before |
Named permissions, faculty scope, locked approvals |
| 03Results |
Before |
One flow from marks to issued results |
| 04Data safety |
Before |
Scheduled off-site backups and a full archive |
| 05Security |
Before |
University-hosted, university-held keys |
| 06Payments |
Before |
Bank-integrated, reconciled automatically |
Grades & results
From marks to issued results in one flow
The problem: spreadsheets passed between offices, GPAs worked out by hand, errors found after issuance.
-
1
Enter marks
Data entry per course, scoped to the faculty
-
2
Preview sheet
See the full result sheet before it counts
-
3. Approve & lock
Approval freezes the marks behind it
-
4
Rules applied
GPA and academic remarks worked out by rule
-
5
Issue
Published to every student's portal at once
academic status codes (pass, repeat, resit, freeze, dismissal and more) applied by rule
GPAs calculated by hand; regular, resit and Sup & Sub sheets share one set of rules
source of truth: the approved sheet is what students, transcripts and finance all read
Try it in the demo: sign in as grades.admin to
generate and approve a result sheet, or as
data.entry to enter marks for one faculty.
Records
Every action has an owner and a purpose
The problem: shared logins, deleted rows and edits no one could trace back to a person.
-
Role
Registrar, data entry, finance officer…
-
Permission
One narrow, named right per action
-
Scope
Only the faculties a user is given
-
Action
Allowed, recorded, attributable
-
Permissions, not job titles
The system checks a named permission on every request, never a role name or a promise.
-
Approved means locked
Once results are approved, the marks behind them cannot be edited. Corrections go through amendments.
-
Destruction is designed out
Bulk deletes are blocked; records change through actions with a stated purpose, not raw edits.
Try it in the demo: data.entry sees the Faculty of
Engineering only, and finance.discounts can give
discounts but not record payments.
Security & data safety
Your data. Your servers. Your keys.
Outside vendors, hosts and integrators held access to student and staff records the university could not control or revoke. University System Suite runs where the university decides, and nothing sensitive is ever one failure away.
-
Runs on the university's own infrastructure
Deployed in-house. No third party hosts, reads or holds the data.
-
Signing keys held by the university
Sessions are signed with the university's own keys, and keys can be rotated at any time.
-
Integrations get only what they need
Connected systems like the LMS read a fixed set of tables. Passwords are never shared.
-
Least privilege by default
Every user, internal or external, starts with nothing and is granted only named permissions.
-
Live system
Every record, current and in use
-
Periodic backups
Automatic, scheduled, encrypted, kept off the main server, and restores tested
-
Long-term archive
Every year's records and results, preserved and retrievable
Finance
Payments that settle themselves
The problem: queues at the cash desk, paper receipts, and finance matching bank statements by hand.
Students & staff
Pay fees or receive salaries
Finance
Fees, dues and receipts in one ledger
Partner banks
Payments confirmed and reconciled
-
Pay at the bank or online
A payment is recorded against the student as it clears, with no receipt to carry back.
-
Partial payments & discounts
Instalments, discounts and per-student fee plans, each with its own permission.
-
Past dues carried forward
Unpaid balances follow the student into the next year automatically.
-
Multiple currencies
Fees set per faculty and acceptance type, in the currencies the university keeps.
Try it in the demo: student BE-25-1004 carried an
unpaid semester into past dues, so a result is withheld until it
is paid.
Modules
Every office on the same system
One sign-in, one set of records. Each person sees only the workspaces their role opens.
In the demo
-
Teachers & staff portal
One sign-in for teaching and administrative staff. Each person sees only the tools and faculties their role grants.
-
Grades & results
Marks entered, previewed, approved and locked. GPAs and status codes applied by rule, then published to every student at once.
-
Finance
Fees by faculty and acceptance type, partial payments, discounts and receipts in one ledger. Past dues carry forward.
-
Admissions
Applications, medical checks and interviews, stage by stage, with an applicant portal for new students.
-
Students portal
Each student's profile, curriculum, results and dues, from any device. Everyday questions no longer need an office visit.
-
Website + CMS
The public website (faculties, news, leadership and pages) run by its own content team, each editor with their own permissions.
Added per university
-
LMS
Not in this demoCourses, material and assignments online, kept in step with live student and curriculum data, so every course reflects who is actually enrolled.
-
HR
Not in this demoStaff records, appointments and contracts in one place, tied to the accounts staff sign in with. Salaries go out through the bank link.
-
E-library
Not in this demoBooks, papers and course readings in digital form, reachable on and off campus with the same university account.
How it's built
Secure, automated, always current
-
DevSecOps
Security is checked at every step of building and shipping, not bolted on after.
-
Secure by design
Least privilege, signed sessions and locked records are the default.
-
CI/CD
Every change is tested automatically and released in small, safe steps.
Next steps
See it running
The demo is live, with staff, student and applicant accounts included.
-
01
Guided walkthrough
We tour the demo with your registrar, results and finance teams.
-
02
Pilot on your data
One faculty, one semester, on your own infrastructure.
-
03
Go live
Roll out faculty by faculty, with your staff trained and your keys in hand.