Catholic University of South Sudan

CUofSS-UniMIS System Accounts

Every login in the University Management Information System, grouped by the portal it signs in through. Companion to the user manual — the manual explains what each role does, this lists the accounts that hold them.

34 logins · 5 portals One shared test password
Re-verified 27 Jul 2026
§ 1

The shared password

Every account on this page signs in with the same password while the system is in testing.

34 logins 23 back office 4 deans & HODs 3 lecturers 2 students 1 applicant 1 role-test
§ 2

Which portal to use

One person, one sign-in — but the address depends on who you are. Using the wrong portal is the most common reason a correct password appears to fail.

Admin back office

admin.cuo-ss.sektechsoftsolutions.co.ke/admin/login

Everyone in §3–§6. Sign in with your email address.

Staff portal

staff.cuo-ss.sektechsoftsolutions.co.ke

Deans and heads of department (§7). Same email and password as the back office.

Lecturer portal

lecturer.cuo-ss.sektechsoftsolutions.co.ke

Teaching staff (§8) — marks, class lists, attendance.

Student portal

student.cuo-ss.sektechsoftsolutions.co.ke

Students (§9). Sign in with a student number, not an email. Same password as everyone else.

Applicant portal

apply.cuo-ss.sektechsoftsolutions.co.ke

Prospective students (§10). Applicants normally register themselves.

Tip

Signed in on one portal, you are signed in across all of them — the portals share a single account. What differs is what each one shows you.

§ 3

Leadership & governance

The offices that approve, endorse and oversee — they mostly read and sign off rather than enter data.

Portal›Admin back office

IDRoleSign in withPassword
83Vice Chancellor
Vice Chancellor
84DVC — Academic Affairs
DVC Academic Affairs
81DVC — Admin & Finance
DVC Admin & Finance
79Senate
Senate Member
90Academic Board
Academic Board Member
88Campus Director
Campus Director
89QA Officer
QA Officer
2Super Admin
Super Admin
3Super Admin
CUofSS Super Admin
69Super Admin
Demo Administrator
§ 4

Registry & admissions

Student records from application through registration to graduation, plus examinations and student welfare.

Portal›Admin back office

IDRoleSign in withPassword
5Registrar
Misa Registrar
85Academic Registry Staff
Academic Registry Staff
76Admissions Officer
Alice Nyagoah
86Exams Officer
Exams Officer
87Dean of Students
Dean of Students
§ 5

Finance

Fees, invoices, payments and clearance. Two of these are real staff accounts rather than test ones.

Portal›Admin back office

IDRoleSign in withPassword
49Finance Manager
Ignatious Nguyo real account
54Finance Officer
Ignatious Nguyo real account
77Bursar
Michael Garang
82Cashier
Cashier
§ 6

HR, ICT & library

Staff employment records, system administration, and the library office that signs off its own clearance step.

Portal›Admin back office

IDRoleSign in withPassword
4HR Manager
CUofSS HR Administrator
80HR Officer
HR Officer
78ICT Admin
David Majok
93Librarian
University Librarian · CUSS-STF-0093
Note

The Librarian account was added on 25 July 2026. The role already existed with library clearance permissions, but no person held it — so the Library step of student clearance had nobody able to action it.

§ 7

Deans & heads of department

Academic leadership. They moderate and endorse marks for their own department or faculty, and see only their own scope.

Portal›Staff portal

IDRoleSign in withPassword
70Dean — ICT
Dr. Grace Deng · DEMO-STF-002
71HOD — ICT
Dr. John Lado · DEMO-STF-003
72HOD — Education
Dr. Mary Akol · DEMO-STF-004
73HOD — Agriculture
Dr. Peter Deng · DEMO-STF-005
§ 8

Lecturers

Teaching staff — class lists, attendance, continuous assessment and examination marks for the courses they are assigned.

Portal›Lecturer portal

IDRoleSign in withPassword
74Lecturer — ICT
James Otim · DEMO-STF-006
75Lecturer — Education
Rebecca Aluel · DEMO-STF-007
46Lecturer
Lecturer Portal
§ 9

Students

Students do not sign in with an email address. They use their student number — the registration or admission number works too.

Portal›Student portal

IDStudentSign in withPassword
10Emmanuel Ochan
BIT · CUSS/BIT/JUB/26/00001 · born 2003-04-15
11Grace Nyibol
BED · CUSS/BED/JUB/26/00002 · born 2004-09-22
Tip

Both students are already activated, so they can sign in directly. The dates of birth above are only needed if you want to walk through the self-service Activate my account wizard, which asks for a student number and date of birth.

§ 10

Applicants

Prospective students who have not yet been admitted. The applicant portal is normally self-service — people register themselves and verify their own email.

Portal›Applicant portal

IDRoleSign in withPassword
92Applicant
Demo Applicant
§ 11

Role-test account

One further account exists that is not tied to any real person or student record.

IDRoleSign in withPassword
91Student
Role-holder for permission testing
Care

This account carries the Student role but has no student record behind it, so it cannot sign in to the student portal by student number. It exists to test what a student-level account is allowed to reach. Use the two real student logins in §9 for anything you actually want to see working.

§ 12

What changed

Recent changes that affect how these accounts behave.

12.1  The back office is now staff-only

From 27 July 2026, every page under the admin back office requires a staff account. All 24 staff roles have it; Student and Applicant do not.

AccountAdmin back officeIts own portal
Any of the 24 staff roles (§3–§8)Works as beforeWorks
Student (91) and Applicant (92)RefusedWorks

If you sign in as a student or applicant and then try an /admin address, you will be turned away. That is deliberate, not a fault. Nothing changed for staff.

12.2  Account history

  • 22 July 2026 — the demo accounts were moved off their old seeder password onto the shared one, so every login now uses Admin@12345.
  • 25 July 2026 — the Librarian account (93) was created so the Library clearance step has someone able to action it.
  • 27 July 2026 — every account re-verified by a real sign-in attempt; the role-test account (91) documented here for the first time.
  • 27 July 2026, later — all 32 passwords were reset by a seeder re-run and then restored (§12.3).

12.3  The 27 July lockout

For part of the afternoon every account on this page was refused at sign-in, including the Registrar, Bursar and Super Admin.

What happenedDetail
SymptomCorrect credentials rejected with "The admin credentials are not correct". Nothing else on the system was affected.
CauseThe demo-data seeder was re-run. It rewrote the password of every existing account back to its own value, silently — passwords stopped being Admin@12345.
FixAll passwords restored to Admin@12345, and the seeder changed so it now sets a password only when creating a new account. Re-running it no longer touches an existing login — staff, student or applicant.
Also foundThe first repair covered the staff accounts but missed the two student portal logins, which stayed on the old seeder password while everything else moved. Corrected 27 July, and now covered by the same create-only rule.
VerifiedThe seeder was re-run deliberately afterwards; all 32 accounts still signed in. Four accounts were then tested through a real browser sign-in.
If a login is refused again

Before assuming the password on this page is wrong, ask whether a seeder or demo-data reset has just been run. That is what happened here, and it looks identical to a wrong password. Any administrator can reset an account from Admin › Governance › Users.

Before go-live

This page describes a system in testing. Before the university starts using it for real: purge the demo and test accounts, give every remaining account its own password, and take this page down.