This view uses the existing Organization panels. Your secure piSun session confirms the Organization type and each person’s authorized position and scope after sign-in.
President · Provost · Dean · Department chair · Registrar · Faculty / instructor · Researcher · Lab manager · Teaching assistant · Administrative staff · Human resources staff · Payroll staff · Security staff · Other employee
Students: enrollment and CampusID; academic and resource access remains separately authorized.
Optional scope: Campus · College · Department · Program · Course · Class · Lab.
Preparing a position does not appoint an official, record an election, grant payroll or academic authority, or authorize entry.
Use the existing Academic Access authority scope to submit provisional grades, revise them before student acceptance, review student challenges, and post only grades that the student Patron has accepted.
Submitted → provisional → student accepts or challenges → challenge resolved when needed → student accepts → authorized persistence. No instructor, teacher, course administrator, or academic administrator can skip the student acceptance boundary.
Authorized instructors, teachers, faculty, course admins, or academic admins submit grades only inside their assigned Organization and course/class scope.
The grade is not yet permanent and is sent to the student Patron for individual review.
The original submitter may change score, grade value, or feedback while the grade remains pending student acceptance and the submitter still has the same academic scope.
Another instructor with general course access cannot silently replace that submitter's grade.
A challenged grade is frozen from permanent posting. Authorized academic staff review the challenge and may retain or revise the result.
After resolution, the grade returns to the student for a fresh acceptance.
The permanent Student account record accepts only a grade already in the student-accepted state and only through an authorized backend persistence path.
The admin UI cannot directly bypass PSOP and write an unaccepted grade into the permanent record.
This queue is scoped by course/class authority. A submitter sees the grades they are authorized to manage, not unrelated student records.
Issue provisional grades inside assigned academic scope, revise unaccepted grades when you are the original submitter, review challenges when authorized, and request persistence of student-accepted grades.
Enter the student's desktop, access unrelated courses, alter another submitter's pending grade without a defined authority path, or permanently post an unaccepted or challenged grade.
Grade administration is another controlled view over the existing University / K-12 Admin Panel authority model. Course, class, instructor, teacher, administrator, student, assignment, grade, challenge, and persistence authority remain separately scoped underneath the UI.
