Step-up required
Step-up required3
High-risk mobile approvals requiring fresh staff auth.
BPPE Career
Finance
What is this page?
This page proves staff mobile approval review for prepared inbox items, including due-date ordering, high-risk step-up authentication, two-person approval boundaries, and server-owned audit recording.
Use Sev2 if high-risk staff approvals appear complete without fresh step-up, audit context is missing, two-person approval is bypassed, approve-all includes money or official-record items, or production record/money/message writes appear enabled. Use Sev3 for inbox ordering, evidence, blocker, mobile step-up, or route issues; use Sev4 for labels or layout feedback. This panel does not submit a support case.
Sev1: Critical outage or data-risk emergency
Target: 1-hour response, 24/7 paging during pilot
Sev2: Major workflow blocked
Target: 4 business hours
Sev3: Standard product question or non-urgent issue
Target: 1 business day
Sev4: How-to, cosmetic, or future enhancement
Target: 2 business days
These preview controls are placeholders. Real AI answers, search, walkthroughs, and support submission come in later tickets.
Static proof preview
Real notification feeds, delivery, and preferences arrive in a later ticket.
Morgan Bursar
morgan.bursar@otto-fixture.test
Switch local proof role
This changes only the local shell proof. Production role changes remain server-validated future work.
Search is a keyboard-focusable skeleton. No real index or permissioned search results are implemented in this ticket.
Phase 20 mobile staff approval proof
Review staff phone approval inbox behavior, fresh step-up authentication, two-person boundaries, and server-owned approval audit records.
Otto Fixture BPPE Career School - staff approvals
Finance ยท Morgan Bursar
Staff mobile approval proof
Local proof that finance, registrar, and compliance staff can review approval inbox items on a phone while high-risk decisions stay behind fresh step-up authentication and server-owned audit recording.
Approvals with step-up
The phone can launch review and show the evidence packet, but the final approval record is not complete until server confirmation.
Step-up required
Step-up required3
High-risk mobile approvals requiring fresh staff auth.
Approve all eligible
Approve all eligible2
Standard-risk items that passed every evidence check.
Two-person rule
Two-person rule1
Money-impact item blocked until a second reviewer acts.
Phone width
Phone width390 px
Proof target for staff approval review on phone.
Finance phone
Morgan Bursar sees high-risk items, evidence, blockers, and step-up state before acting.
Due now
390 pxStatus review, failed-step replay, standard reminders, and two-person payment work sorted by due date.
Step-up check
Not complete until server confirms
Approval controls stay preview-only until the server validates session, MFA, role, two-person rules, and evidence hash.
Approval inbox
Omar Reyes
Prepare staff review task for Omar Reyes after lifecycle status changed to withdrawn.
Due
Oct 13, 7:00 AM
Assigned
Registrar Lead - Registrar
Evidence
3
Maya enrollment packet
Prepare replay of failed urgent email resend after the fake inbox adapter issue is resolved.
Due
Oct 13, 8:00 AM
Assigned
Compliance Ops - Compliance
Evidence
3
Maya Patel
Prepare advisor notice, advisor to-do, calendar check-in draft, and student SMS draft for Maya Patel.
Due
Oct 13, 9:00 AM
Assigned
Ari Advisor - Advisor
Evidence
3
Approval needed: Maya Patel advisor check-in is ready by 4:00 PM.
Medical program cohort
Prepare Thursday lab-day reminder drafts for active medical students with quiet-hour and consent checks.
Due
Oct 13, 10:00 AM
Assigned
Sam Director - School administrator
Evidence
3
Approval needed: weekly lab reminder drafts are ready by 5:00 PM.
Daniel Kim
Prepare finance follow-up after Daniel Kim payment failure, with no ledger mutation or payment retry.
Due
Oct 14, 3:00 AM
Assigned
Finance Ops - Finance
Evidence
3
Step-up policy
A finance staff member has a fresh MFA-satisfied session inside the five-minute window.
Auth time
2026-10-13T12:28:00.000Z
The approval stays blocked when authentication is older than the step-up max age.
Auth time
2026-10-13T12:24:59.000Z
A verified factor is not enough; the current session must be MFA-satisfied.
Auth time
2026-10-13T12:29:00.000Z
A missing session blocks approval before item risk, evidence, or role rules are checked.
Auth time
No authentication time
Approval audit preview
Approver
Registrar Lead
Device
iPhone 15 Pro PWA
Would record at
2026-10-13T12:30:00Z
Evidence hash
proof-approval-omar-status-review
Later approval would record registrar identity, step-up context, evidence hash, and status-change snapshot.
Disabled actions
Approve high-risk item without step-up
Official-record, money-impacting, and failed-step approvals must pass fresh step-up before the server can record a decision.
Approve with stale authentication
The five-minute step-up window has to be current at the moment of approval.
Approve without completed MFA
Staff roles require an MFA-satisfied session before sensitive mobile approvals.
Approve without an active session
A missing session blocks the step-up policy before item-specific rules are evaluated.
Approve own prepared money item
Two-person approval blocks the preparer from approving the payment follow-up they prepared.
Use approve all for high-risk items
Money, official-record, failed-step, blocked, and two-person items stay one-by-one.
Write approval record from local proof
The page previews who, device, time, and evidence hash, but does not persist audit rows.
Mutate student status, refund, grade, or credential
Approval preview cannot alter official records, issue refunds, retry payments, or change grades.
Send production push, email, or SMS
Notification previews are local fixtures until production adapters and consent checks run.
Hide evidence before approval
Every mobile approval keeps evidence, blockers, and prepared-result snapshots visible.
Approve while offline
Sensitive approvals require a live server round trip for step-up and audit recording.
Suppress device and time context
The future audit record must include approver identity, device context, timestamp, and evidence hash.
Proof boundary