Superadmin Guide

Welcome

This guide covers the superadmin role in the EAC Portal. It is limited to system administration tasks that matter to portal operations.

What superadmin access is for

Superadmins manage the platform at a system-wide level.

Their work is mainly performed through the Django admin area.

Main responsibilities

A superadmin can manage:

• users

• schools

• departments

• school admin assignments

• students

• academic records

• level records

• work experiences

• organizations

• notification records

• user action logs

User administration

From the user administration area, a superadmin can:

• create users

• update user details

• activate or deactivate accounts

• grant or remove staff status

• grant or remove superadmin status

• review login and account history fields

Institution administration

Superadmins can:

• create schools

• update school details

• create departments

• manage department accreditation status

• assign school administrators to institutions

Student and record oversight

Superadmins can review and manage:

• student profiles

• academic records

• level records

• work experience entries

• organizations

Students cannot update their own username, name, email, or student profile details from the student portal. Superadmins can make system-wide corrections through the admin area, while routine institution-level corrections should usually be handled by the responsible staff user.

Notifications and audit trail

Superadmins can review:

• notification records sent through the portal

• user action logs that record key account actions

This helps with operational monitoring and support.

Printing admin pages

The admin area includes print styling for view and list pages. When a browser print is started, navigation, action buttons, pagination controls, and other screen-only controls are hidden so the printed output focuses on the records.

When to use superadmin access

Use superadmin access for:

• system-wide corrections

• institution setup

• user and permission management

• high-level oversight

Avoid using it for routine institution-level work when normal staff workflows are sufficient.

Frequently Asked Questions