Who This Topic Is For
Users evaluating premium automated engagement paths or managing partner workflows.
Help
Premium And Partners Help
Support guidance for premium assessment pathing, intake and status tracking, and affiliate/partner workflow questions.
Prerequisites
Before You Start
Use this checklist to make sure the workflow guidance applies cleanly to your current task.
- You can define whether your need is self-serve automation or scoped premium engagement.
- You can describe the assurance level and business timeline for the engagement.
Playbook
Step-By-Step Guidance
Follow these steps in order for a reliable and repeatable outcome.
Confirm whether premium is the correct path.
Use premium assessments when you need scoped higher-assurance outcomes that go beyond routine recurring automated checks.
Align stakeholders on current premium availability.
Penetration Test workflow is live. Comprehensive Assessment remains staged as next rollout, so planning should reflect current availability state.
Cloud beta is currently a waitlist and demand-validation path rather than a generally available managed scanning workflow.
Define scope and expected deliverable outcomes.
Set clear scope boundaries and intended business outcome so the selected premium route matches what stakeholders actually need.
Use the premium lifecycle after order creation.
Track the premium order through intake, payment, verification, automated execution, and report delivery so stakeholders do not confuse an order confirmation with a completed engagement.
Route partner operations through the correct workflow.
Use the affiliate portal for approved referral tracking, qualified rewards, and payout lifecycle visibility.
Operations
Operational Playbook
Use this long-form guidance to execute the workflow consistently across planning, implementation, and validation.
Select Premium Path Based On Assurance Objective
Premium engagement decisions should begin with assurance objective clarity. Define what confidence outcome is required, which stakeholders depend on it, and what timeline constraints apply. Premium assessments are appropriate when scoped, higher-assurance outcomes are needed beyond routine automated cadence. If the objective is still category-specific or early exploratory validation, standard tool and scan workflows may be more efficient. Objective-first selection prevents unnecessary escalation and keeps premium capacity focused on the highest-value use cases. It also improves stakeholder alignment because expectations are grounded in explicit goals rather than generic desire for deeper review.
Align Stakeholders On Live Versus Staged Availability
Execution planning must reflect current product availability state. Penetration Test workflow is live, while Comprehensive Assessment remains staged for future rollout. Communicate this early so commercial and technical stakeholders do not plan timelines around unavailable paths. When teams fail to align on availability, they create avoidable schedule risk and expectation mismatch. Include availability confirmation in kickoff notes and repeat it during planning checkpoints. This simple control improves reliability and helps preserve trust with external and internal stakeholders who rely on accurate delivery commitments.
Define Scope Boundaries Before Engagement Starts
Comprehensive premium outcomes require clear scope boundaries before work begins. Specify which assets, environments, and objective criteria are included, and identify what is explicitly out of scope. Ambiguity here is the most common source of mid-cycle rework and delayed sign-off. Scope definition should also include communication cadence, expected deliverables, and escalation contacts. When scope is clear, both teams can execute confidently and evaluate outcomes against agreed criteria. This improves quality and reduces negotiation during delivery. For partner-assisted workflows, shared scope understanding is especially important to preserve referral trust and predictable operations.
Use The Intake, Checkout, And Queue Workflow Deliberately
Premium Assessments are not just landing pages. The live product includes intake capture, secure checkout for the current live tier, domain verification, and queue or status tracking after the order is created. Teams should treat those stages as one connected workflow so stakeholders know when payment is complete, when automated testing is underway, and when the evidence-backed report is ready. This reduces confusion between self-serve scans and premium engagements because the premium path has its own lifecycle and delivery expectations.
Operate Partner Workflow Through The Correct Portal Path
Affiliate and partner operations should run through the dedicated portal workflow to maintain consistent attribution, reward tracking, and payout visibility. Avoid informal side channels for referral-state decisions, because they fragment records and create reconciliation issues. Define who within your organization can submit partner updates and who verifies payout-relevant events. This governance helps avoid disputes and supports cleaner commercial reporting. If portal behavior does not match expectation, escalate with reproducible context and account identifiers so support can resolve quickly. Structured partner operations reduce overhead and preserve relationship quality.
Build Early Escalation Habit For Commercial Edge Cases
Premium and partner workflows can involve cross-functional dependencies that are not obvious at first contact. If uncertainty appears around scope, path status, referral state, or timeline expectations, escalate early with complete context. Early escalation prevents last-minute coordination breakdowns and keeps delivery confidence high. Include intended objective, current blocker, expected milestone, and affected stakeholders in the request. Over time, this habit creates a smoother operating model where commercial and technical workflows reinforce each other instead of competing for urgency.
Measure Premium And Partner Outcomes For Continuous Improvement
A comprehensive premium and partner help model should include outcome measurement, not only process steps. Track indicators such as time to scope alignment, time to delivery milestone completion, quality of escalation context, and recurring partner workflow issues. Review these indicators on a defined cadence so patterns are identified early and process adjustments are data-driven. When one category repeatedly causes friction, update guidance and intake templates so future cycles improve. Outcome measurement supports both operational quality and trust with stakeholders, because improvements are visible over time. It also makes support interactions more effective since teams can reference prior patterns rather than troubleshooting each case as if it were entirely new.
Validation
Validation Checklist
Use this checklist to confirm the workflow was completed correctly.
- Selected path aligns with assurance and scope requirements.
- Stakeholders understand live vs staged premium status.
- Scope and expected outcomes are documented before engagement start.
- Premium lifecycle status is visible after the order is placed.
- Partner account is using the correct portal workflow.
- Commercial edge cases are escalated before deadlines.
Troubleshooting
Common Problems And Fixes
If something does not match expectation, check these common failure modes first.
Assuming premium path is required for all concerns
Many concerns are resolved through tools and normal scan workflows; reserve premium for scoped higher-assurance needs.
Using wrong route for partner operations
Use the affiliate portal workflow for referral and payout tracking needs.
Planning around staged capabilities as if already live
Confirm current availability state first so timelines and stakeholder commitments match what is live today.
Treating cloud beta waitlist as a fully live cloud scanning product
The cloud beta path is currently a waitlist used to validate demand and identify qualified early testers. It should be described as interest capture, not as a generally available scanning workflow.
Starting engagement without clear scope boundaries
Define expected outcomes and scope up front to prevent ambiguity during delivery and review.
Assuming checkout means the report is already ready
Use the premium queue and status workflow after order creation so payment, intake, verification, automated execution, and final report delivery are tracked separately.
Navigate
Related Pages
Use these links to continue your workflow without losing context.
FAQ
Premium And Partners Help FAQs
Common questions for this topic.
Next Recommended Action
Continue to the best next page based on where you are in your workflow.