Admissions platform for universities
International admissions, run from one platform.
Applications, documents, partner agencies and fees in a single system. Deploy it for one university, or for a whole country’s network of universities.
- 6
- user roles
- 5
- pipeline stages
- 2
- deployment models
Platform
Everything admissions needs, already connected
Every student has one record: application, documents, agency and payments. Nothing lives in spreadsheets or inbox threads.
Application pipeline
Submitted, under review, offer, enrolled. Each application’s status is visible to everyone who needs it.
Document checks
Checklists per programme, verification status per document, and secure storage for every applicant.
Agency network
Partner agencies manage their own students inside the platform. Every application keeps its attribution.
Role-based access
Students, universities, agencies and admins each get their own portal. Parents and embassies get read-only views.
Fees and payments
Application and commitment fees are collected and reconciled in the platform, not tracked by hand.
Housing beta
An optional module for universities that allocate student accommodation alongside admissions.
Deployment
Two ways to deploy
The engine is the same in both. Start with one university and join a national network later, or launch the network from day one.
Single university
Your university runs its own portal, independently.
- Your domain, branding and admissions team
- Your own programme catalogue and pipeline
- No dependency on a wider rollout
National programme
One shared portal with many universities inside it.
- Each university gets its own workspace
- One agency network shared across all universities
- Central oversight for a ministry or consortium
- Onboard universities one by one, or all at once
How it works
From first call to live admissions
-
Talk to us
Tell us about your university or national programme and how admissions work today.
-
We configure your instance
Programmes, roles, branding and document templates, set up around your current process.
-
Your team onboards
Staff, partner agencies and students get accounts and start submitting applications.
-
We run the platform
Hosting, updates and support stay with us. Your team focuses on admissions.
Roles
Six roles, each with its own view
Student
Browses programmes, uploads documents, tracks the application and pays fees.
University
Reviews applications, verifies documents, updates programmes and templates.
Agency
Submits and manages applications on behalf of its students.
Admin
Manages users, universities and agencies across the instance.
Parent read-only
Follows their child’s application status. No documents, no edits.
Embassy read-only
Sees the status of applicants who are its citizens. Nothing else.
FAQ
Common questions
Can we deploy Enrollum for just one university?
Yes. A single-university deployment runs independently, with its own domain, branding, programme catalogue and admissions team.
Can Enrollum run admissions for a whole country?
Yes. In the country-wide model, a national portal hosts many universities. They share one agency network and central oversight, and each keeps its own workspace.
Is it already used in production?
Yes. Enrollum is the engine behind a live admissions platform. We package that same engine for other universities and countries.
Who can see student documents?
University staff see only applicants to their university. Agencies see only the students they added. Parent and embassy accounts never see documents.
How long does setup take?
It depends on scope. One university is quicker than a national rollout. Contact us and we’ll give you a realistic timeline.
See it running on your programmes
Tell us about your university or national programme. We’ll get back to you directly.