Sales fit and plan path
Use this when public pages do not answer whether the product fits the target, buyer, platform, plan or agency path.
- Target domain or platform
- Buyer type and commercial journey
- Scan, monitoring, fix-credit or agency intent
Routing
WebRiskOps Routing - plan, billing, scan and security questions
Use this page to choose the right async route when the product page you are on does not already show the next step. Standard scans, payments, reports, fixes and monitoring still start inside the app workflow.
Routing categories
Choose the route that owns the state
Each route points back to the app workflow or public boundary that should hold the source of truth before a structured request is submitted.
Account access and login
Use account-owned pages for access state, team roles, verification, current account selection and profile settings.
- Account name when visible
- User role or invitation state
- Verification, login or current-account blocker
Billing, payments and credits
Use billing for plan state, subscriptions, credits, refunds, service credits, disputes and checkout confirmation.
- Package, subscription or credit item
- Payment or provider status shown in app
- Refund, service-credit or dispute record
Scan and report questions
Use scan and report pages for project scope, scan state, evidence artifacts, findings, quality gates and blocked report states.
- Project and target URL
- Scan status or report state
- Finding, evidence artifact or quality gate
Fix, retest and access mode
Use the report and fix workflow records for finding status, credit eligibility, access mode, ticket-only fallback and retest outcome.
- Finding or fix task
- Requested access mode and customer policy
- Retest expectation or result
Monitoring and alerts
Use project and settings pages for monitoring subscription state, alert cadence, latest scan, notification preferences and high-risk changes.
- Monitored project
- Alert type and cadence
- Latest scan or notification setting
Agency and client workspaces
Use agency workflow pages for client authorization, white-label behavior, shared reports, branding and agency billing responsibility.
- Agency account and client name
- Client authorization state
- Branding, report sharing or recurring scan need
Unsupported scope
Use authorization guidance when a requested target, crawl path, business type or access model is blocked before scanner work starts.
- Requested target and path
- Blocked reason shown in app
- Revised owned or authorized scope
Product security disclosure
Use this only for concerns about WebRiskOps itself, separated from customer scan findings and ordinary workflow questions.
- Affected WebRiskOps surface
- Impact and reproduction outline
- Private handling request without public exploit details
Product security disclosure boundary
Do not include credentials, payment method details, private keys, provider tokens or public exploit instructions in ordinary routing context.
- Separate product-security issues from customer findings
- Keep secrets out of request text
- Use traceable workflow records when available