Role-specific navigation and actions are projected from /api/permissions/matrix. The browser cannot supply tenant, entity, role, signer, or forwarded-header authority; never-allowed actions are omitted from the shell instead of rendered disabled.
Matrix source
api_server_derived_from_session_registry_context
Primary role lane
pci_operator from server matrix metadata
Visible actions
8
Suppressed actions
1 action(s) withheld without client-side disabled controls.
Viewer role accepted
false
Signer input accepted
false
Step-up reauthentication handoff
When the server-derived permission matrix marks an action as requiring step-up, this shell sends the operator to the same-origin PCI API/BFF step-up route. The browser never constructs Autheory authorize URLs and never supplies tenant, role, principal, subject, MFA, freshness, or permission authority.
Override inherited answerReauthenticate
Only sensitive_action=answer.override is sent as a non-authoritative retry hint.
Queue audit exportReauthenticate
Only sensitive_action=operator.audit_export is sent as a non-authoritative retry hint.
Step-up initiate
/api/session/step-up
Callback boundary
/api/session/callback is API/BFF-owned after provider reauthentication.
Allowed browser hint
sensitive_action / action only; the API must re-check session, CSRF policy for unsafe service retries, tenant registry, permissions, and freshness.
Visible server-allowed actions
Action
Category
Step-up
Reason
Review tenant
tenant
server authorized
role_allows_tenant_review
Review evidence package
evidence
server authorized
role_allows_evidence_review
Create evidence metadata intake
evidence
server authorized
role_allows_evidence_upload_metadata
Answer questionnaire
assessment
server authorized
role_allows_answer
Override inherited answer
assessment
server step-up required
operator_step_up_required
Invite submerchant
onboarding
server authorized
operator_scope_review_required
Save workflow state
workflow
server authorized
role_allows_workflow_metadata_save
Queue audit export
audit
server step-up required
role_allows_operator_audit_export_metadata
auth.session_refreshed
Module status
Data Collectionenabled / primary
Data Collection is enabled by trusted session context.
Monitoringenabled / integrated
Monitoring is enabled by trusted session context.
Assessment follow-up neededSAQ A
Assessment follow-up needed
Use the shared Data Collection workspace to finish answers, request evidence metadata, and resolve review readiness without moving authority into the browser.
△Needs attention
missing_evidence_metadata
unresolved_review_finding
Assessment service details
Assessment data services
Live assessment workspace
read-only-load
Loading the current assessment bundle, responses, findings, remediation, and readiness from same-origin APIs.
Use these controls to save an answer, complete the current assessment, or request an evidence follow-up through the same-origin API. Tenant, entity, cycle, evidence, document, and account authority stay server-derived.
Assessment action refs
save_api
/api/assessments/responses/save
complete_api
/api/assessments/complete
evidence_api
/api/evidence/requests
csrf_cookie
__Host-pt_pci_csrf
Last API result
Waiting for operator action.
Questionnaire controlsCSRF-bound
Control answer workbench
⏳Ready for review
Work the concrete questionnaire controls for this cycle. Each row can save an answer or request evidence through the same-origin assessment APIs; tenant, cycle, evidence, and account authority remain server-derived.
Per-control Save answer and Request evidence workbench
Control
Section
Answer state
Evidence state
Actions
Payment-page script inventoryControl refs
requirement_ref
requirement-ref://saq-a/6-4-3
answer_ref
answer-ref://operator/accept-inherited-metadata
Payment flow questionnaire
⏳Ready for reviewready for review
✓Acceptednot required
AOC package evidenceControl refs
requirement_ref
requirement-ref://saq-a/record-only/aoc
answer_ref
answer-ref://operator/accept-inherited-metadata
Payment flow questionnaire
⏳Ready for reviewready for review
✓Acceptedaccepted ref only
Monitoring readiness evidenceControl refs
requirement_ref
requirement-ref://saq-a/record-only/monitoring
answer_ref
answer-ref://operator/update-required-metadata
Monitoring readiness questionnaire
▣Blocked — action neededblocked
!Missingmissing
Questionnaire progressSAQ A
Questionnaire response workspace
Responses are loaded as the current assessment summary. Entity, cycle, and evidence authority stay with the service.
✓Acceptedinherited▣Blocked — action neededstale⏳Ready for reviewoverride!Missingevidence required▣Blocked — action neededblocked
△Needs attentionwarningresponse.inherited_answer_staleInherited answer is stale; accept or override from trusted API state before readiness.Validation refs
▣Blocked — action neededblockedresponse.evidence_metadata_missingEvidence metadata ref is missing; content is not rendered in the app shell.Validation refs
Operators can acknowledge the current review finding and queue the next remediation step through the same-origin API. The client submits action intent only; finding, plan, task, evidence, tenant, and cycle refs are server-derived.
Review action refs
finding_action_api
/api/review/findings/acknowledge
remediation_action_api
/api/remediation/plan/actions
csrf_cookie
__Host-pt_pci_csrf
Last review API result
Waiting for operator action.
ReadinessUnsigned export
Readiness and unsigned attestation export
▣Blocked — action needed
State
▣Blocked — action neededblocked
Blockers
missing_evidence_metadata
unresolved_review_finding
stale_inherited_answer
Ready reasons
No ready reasons are asserted by the current workspace metadata.