Skip to content
Ask Otto AI
Help

What is this page?

Mobile staff approvals with step-up

Role aware

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.

Audience
Staff
Current limits
The mobile staff approval proof uses local deterministic fixtures only. It does not persist approvals, record audit rows, mutate official records, issue refunds, move money, retry payments, send notifications, complete production step-up challenges, or bypass server authorization.

Support request boundary

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.

Notifications8

Static proof preview

Real notification feeds, delivery, and preferences arrive in a later ticket.

Morgan Bursar

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

Mobile staff approvals with step-up

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

Mobile staff approvals with step-up

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 required

3

High-risk mobile approvals requiring fresh staff auth.

Approve all eligible

Approve all eligible

2

Standard-risk items that passed every evidence check.

Two-person rule

Two-person rule

1

Money-impact item blocked until a second reviewer acts.

Phone width

Phone width

390 px

Proof target for staff approval review on phone.

Finance phone

Approval inbox

Morgan Bursar sees high-risk items, evidence, blockers, and step-up state before acting.

Due now

390 px

Status review, failed-step replay, standard reminders, and two-person payment work sorted by due date.

Open full approval inboxReview status

Step-up check

  • Recent MFA step-up: Allowed
  • Stale authentication: Stale authentication
  • MFA not completed: Required MFA not completed
  • Missing session: Missing session

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

Due-date sorted mobile review

5 items

Student status change prepared for Omar Reyes

Omar Reyes

Needs review

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

Official recordOne-by-one requiredStep-up required
  • Official student status outcomes cannot be approved through approve-all.
  • Step-up authentication will be required before a future approval can be recorded.

Failed document resend replay needs review

Maya enrollment packet

Needs review

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

Failed stepOne-by-one requiredStep-up required
  • Failed-step replay requires one-by-one review.
  • Replay controls remain disabled until production replay jobs exist.

Advisor check-in prepared for Maya Patel

Maya Patel

Ready

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

Standard riskApprove all eligibleNo step-up required

Approval needed: Maya Patel advisor check-in is ready by 4:00 PM.

Weekly lab reminder prepared for medical students

Medical program cohort

Ready

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

Standard riskApprove all eligibleNo step-up required

Approval needed: weekly lab reminder drafts are ready by 5:00 PM.

Payment follow-up blocked by two-person rule

Daniel Kim

Blocked

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

Money impactTwo-person ruleStep-up required
  • Money-impacting items cannot be approved through approve-all.
  • Two-person rule blocks the preparer from approving their own prepared result.

Step-up policy

Sensitive phone approvals require fresh auth

5 minute window

Recent MFA step-up

Allowed

A finance staff member has a fresh MFA-satisfied session inside the five-minute window.

Auth time

2026-10-13T12:28:00.000Z

Stale authentication

Stale authentication

The approval stays blocked when authentication is older than the step-up max age.

Auth time

2026-10-13T12:24:59.000Z

MFA not completed

Required MFA not completed

A verified factor is not enough; the current session must be MFA-satisfied.

Auth time

2026-10-13T12:29:00.000Z

Missing session

Missing session

A missing session blocks approval before item risk, evidence, or role rules are checked.

Auth time

No authentication time

Approval audit preview

Server will own the final record

Pending decision

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

Unsafe phone approval shortcuts stay off

12 disabled

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

Local review only

No production writes
  • This page uses deterministic local proof data only.
  • It does not persist approval decisions, record audit rows, mutate records, issue refunds, move money, retry payments, send notifications, or bypass server authorization.
  • Step-up challenge launch, MFA enrollment, WorkOS/Supabase session refresh, push delivery, and final audit persistence stay server-owned.
  • Approve-all remains limited to standard-risk items that passed every evidence check.