Module · Read-Only Ops

Ops View

The same Compliance Dashboard surface, with approve/reject actions hidden. Ops staff can monitor queue health, search applications, and view detail — but cannot approve or reject. Reached at /compliance?role=ops.

What this screen is

You will not see this screen.

A least-privilege view for operations staff. Same data, same filters, same drawer — but the decision buttons are removed. Ops can see what's happening without taking principal-level actions.

Same template as compliance.html. The ?role=ops query param (or ca_role=ops session) sets a flag that hides approve/reject controls and changes the header role badge.

Why it exists

SEC Rule 15c3-1 · Principal Supervision Account approval is a principal-only action under FINRA. Operations staff need queue visibility for SLA monitoring but must not have approval authority.

Least-privilege access control A single template with role-gated controls is auditable and reduces drift between the two views.

What is hidden

Approve button
Reject button
Request Info action menu
Reviewer assignment dropdown

Everything else — search, filters, stats, detail drawer, KYC result, eSign envelope status — remains visible.

What the system records

"event": "ops.view", "user_id": "user_ops_17", "application_id": "VEL-009", "viewed_at": "2026-06-21T18:34:00Z"

Live interactive demo · compliance.html?role=ops

Hotspots — Ops View

Role badge shows OPS VIEW — visually distinct from COMPLIANCE
Same data, same drawer — but Approve / Reject / Request Info controls are hidden by role-gated logic