Roles

Each account has one role. The role decides which menus appear in the sidebar and what the person may do. One lecturer can still have several jobs — teaching, academic advising, exam proctoring and supervising — all from the same lecturer account.

At a glanceCopy Anchor Link

How the roles fit togetherCopy Anchor Link

flowchart TD
  A[Admin · whole campus] --> F[Head of Faculty · one faculty]
  A --> O[Admissions Officer · admission]
  F --> H[Head of Program · one study program]
  H --> L[Lecturer · teaching, advising, supervising]
  L --> S[Student]
  P[Partner · own portal] -.->|brings applicants| O
  AP[Applicant · no account yet] -.->|accepted, gets a NIM| S

Each role has a level and a scope. The level orders the roles; the scope says how much of the campus the role covers.

Partners and applicants sit outside this ladder: a partner works in their own portal and only sees the applicants they brought in; an applicant has no account until they’re accepted and become a student.

What the level controls:

• Giving roles — nobody can give a user a role above their own level, or change the role of someone above them.
• Login As — an admin can only sign in as someone at a lower level, never as another admin.
• Scope — a role limited to a faculty or study program only sees and changes that part of the campus.

One lecturer, several jobsCopy Anchor Link

A lecturer account doesn’t change role for these — the job is attached to the student, class or thesis:

AdminCopy Anchor Link

The admin sidebar is grouped by topic:

An admin can also Login As another user to see the application through their eyes when helping them. Every Login As session is recorded in People › Login As Log.

Admissions OfficerCopy Anchor Link

Works in the Admission menus: the candidate list, booth registration and booth events, and payment records of applicants.

PartnerCopy Anchor Link

Partners sign in through the partner login and see their own portal:

A partner only sees the applicants they brought in. Organisations can add their own staff in My Staff.

Head of FacultyCopy Anchor Link

Menus: Requirement Requests, Announcements and Profile. A study program’s academic requirements (for example credit limits or graduation rules) never change directly: the head of program or an admin files a change request, and the head of the faculty approves or rejects it. Only an approved request changes the rules. If the faculty has no head, the request goes to the admin instead.

Head of ProgramCopy Anchor Link

Everything a head of program sees is limited to their own study program. Approvals collects the requests that need their decision — KRS changes, online sessions over a course’s limit and make-up exams (Requests and approvals).

LecturerCopy Anchor Link

Menus: Dashboard, Announcements, Classes, Live Classes, Schedule, My Proctoring, Assessment, My Advisees, Lecturer Request, Supervised Activities, My Department, Profile — plus a Thesis group (Thesis Students, Consultations, Defense Evaluation).

The same lecturer account covers several jobs:

• Teaching — Classes, Assessment, Live Classes, Schedule.
• Academic advisor (dosen wali) — My Advisees, where they review and approve their students’ KRS.
• Exam proctor — My Proctoring lists the exams they supervise.
• Supervisor — Supervised Activities (internships and other activities) and the Thesis group.

StudentCopy Anchor Link

After signing in a student picks a portal:

ApplicantCopy Anchor Link

Applicants don’t have an account. They use the public Admission page to register and Track Application to follow their status. Once accepted and given a student ID, they create their account on Setup Account — see Signing in.