The numbers you are accountable for, at a glance: users, questions, quiz sessions, and anything waiting on you.

1. The two tiles that need action are Pending Payments and Flagged Questions. If either shows a number, someone is waiting — the same counts appear as red badges in the sidebar.
2. Questions by Department shows where the bank is thin. A department with a low count is where new questions are worth the most.
3. Quick Actions jump straight to the jobs you do most, so you do not have to hunt through the sidebar.

The whole question bank — search it, filter it, fix a question, or add one by hand.

1. Filter by department, category and Free/Premium, then use Search for words inside the question text.
2. Edit opens the question with its options and correct answer. Changing the correct answer affects every student who answers it from now on — it does not rescore past answers.
3. + Add is for one-off questions. For anything more than a handful, use Bulk Import instead.
4. Del is permanent. If a question is merely wrong, fix it rather than deleting it, so students keep their history.

Every edit and delete is written to Audit Logs with your name on it.

Load many questions at once from an Excel or CSV file — the fastest way to grow the bank.

1. Pick the department first, then the file. The importer skips questions the department already has, so re-running the same file does not create duplicates.
2. Update existing questions (match on ID) is for corrections: the file must carry the question ID, and matching rows are overwritten in place.
3. Bulk Delete removes everything you select. Read the confirmation count before you accept it.
4. After an import, spot-check a few rows in Questions — a shifted column turns every answer wrong at once.

Import a small test file first whenever the spreadsheet comes from a new source.

Download the question bank or the user list as a spreadsheet, for editing offline or keeping a backup.

1. Excel keeps Amharic text and formatting intact — prefer it over CSV for anything you plan to re-import.
2. Exported question files carry the question ID, which is exactly what the update-by-ID import needs.
3. Users CSV contains personal data. Keep it off shared drives and delete your copy when the task is done.

Lecture notes and PDFs students can read in the app, plus the queue of files they have uploaded.

1. Uploads from students arrive as pending and stay invisible until you approve them.
2. Open the file before approving. Check it is the right department, readable, and not someone else's personal notes with their name and phone number on them.
3. + Upload Book adds a file yourself; it is approved immediately.

Anything you approve becomes visible to every student in that department.

Problems students reported on specific questions — usually a wrong answer, a typo, or a duplicate.

1. Each row shows the question and the reason given. Open the question, decide, and fix it in Questions if the report is right.
2. Resolve clears the flag and the sidebar badge. Resolve it whether or not you changed anything — a flag left open hides the next real report.
3. The same question flagged by several students is usually a genuine error, not a misunderstanding.

Every registered student, with their plan, score and how they signed up.

1. Search by name or email; filter by Free or Premium.
2. TG marks an account linked to Telegram; 💎 Premium shows a paid plan and its expiry.
3. This page is for looking things up. To change a plan use Upgrade User, and to change departments use Change Depts.

Grant premium to one student by hand — for an approved bank transfer, a promotion, or a fix.

1. Enter the exact email the student registered with, choose the duration, and activate.
2. Check All Users first if the email might be mistyped; an upgrade applied to the wrong account has to be undone by hand.
3. For a payment the student submitted in the app, use Payments instead — approving there records the payment alongside the upgrade.

Every upgrade is logged with your name, the account and the duration.

Change which departments a student sees — normally because they picked the wrong one at signup.

1. Load the student by email or user ID, tick the departments they should have, and save.
2. Removing a department hides its questions from them; their answer history is kept and returns if you add it back.
3. Confirm with the student before changing this. It changes what their whole app shows.

Premium payment requests students submitted in the app, each with a payment screenshot.

1. Open the screenshot and check the amount, the date and the receiving account before approving anything.
2. Approve activates premium for the requested period immediately and notifies the student.
3. Reject when the screenshot is unreadable, the amount is short, or the transfer cannot be found. The student can submit again.
4. If you are unsure, leave it pending and ask a senior admin — an approval is far harder to walk back than a delay.

Approvals and rejections are both recorded in Audit Logs with your name.

Everything students have posted in the discussion area, newest first.

1. Search to find a post; replies appear under the comment they answer.
2. Edit is for trimming something inappropriate out of an otherwise useful post; Delete removes it entirely.
3. Remove abuse, phone numbers and exam-leak claims. Leave ordinary disagreement alone — the discussion is most of the value.

Announcements shown to students inside the app — deadlines, maintenance, new content.

1. Write a short title and a one-line message, pick an icon and colour, then save.
2. A notice only appears while it is active. Turn it off the moment it stops being true; a stale notice teaches students to ignore all of them.
3. Keep one active notice at a time unless there is a genuine second thing to say.

Who did what, and when. Every admin action that changes data is recorded here.

1. Each row shows the admin, the action, the affected record and the time.
2. This is where you check before asking anyone anything: who approved that payment, who edited that question, when a material was published.
3. Entries cannot be edited or removed by anyone, including super admins.

Telegram accounts allowed to run admin commands in the bot. Separate from website staff.

1. Add someone by their numeric Telegram user ID — a username is not enough.
2. This grants control of the bot, not this panel. Website access is granted in Staff & Roles.
3. Remove people the day they stop needing it.

Who can open this panel, and how much of it they can use.

1. Grant access to an existing website account by email, then choose a role.
2. Viewer reads only. Moderator also handles flagged questions. Admin adds questions, users and payments. Super Admin adds staff management.
3. Give the smallest role that lets someone do their job; you can raise it in seconds if it turns out to be too tight.
4. A sidebar item someone cannot see is a privilege their role does not include — that is the gate working, not a bug.

Deactivating an account ends its access immediately.

Referral links for the people who recruit students for you, and the signups each one produced.

1. Create Agent Link generates a code and a link belonging to that agent.
2. Only new accounts opened through the link are credited. Existing users clicking it are not counted, so agents cannot claim people who already joined.
3. Click an agent's row to see exactly who they brought in, and whether those people went premium.
4. Deactivating a link stops new signups counting; people already credited stay credited.