Getting Started
Set up organization basics, connect your first project and launch a scan flow that produces actionable outputs for your team.
What this solves
Removes onboarding ambiguity by defining the minimum setup, first-run process and verification checkpoints before team-wide rollout.
Who is this for
- •Teams onboarding Crawlens for the first time
- •Owners responsible for initial project quality baseline
- •Operators who need a safe first production run
Prerequisites
- •Organization and project created
- •Target URLs grouped with clear naming conventions
- •Required access roles assigned for scan and review
Step-by-step
1. Create your baseline scope
Pick a representative URL set for critical templates and set scan cadence that matches release frequency.
2. Run initial scan and validate outputs
Execute the first scan, verify snapshot completion and confirm artifacts are available for both desktop and mobile.
3. Define alert and ownership policy
Assign alert recipients and map owner teams to changed areas to reduce triage delays.
4. Lock rollout checklist
Document your go-live checklist so every future project follows the same onboarding quality bar.
Operational outputs
- •Initial snapshot set with baseline references
- •Owner mapping for incident triage
- •Repeatable onboarding checklist for new teams
Plan availability
- •Core onboarding and first scan flows are available across plans
- •Operational depth and quota envelopes scale by plan tier
- •Enterprise plans add governance and wider rollout controls
Limits and guardrails
- •Start with a constrained URL set before expanding coverage
- •Avoid mixing experimental and production URLs in one baseline set
- •Track ownership before enabling broad alert fan-out
Expected outcome
- •Team reaches first-value output in the same day
- •Baseline and responsibility model is documented
- •Future scans run with lower operational friction
Troubleshooting paths
- •If scans stall, check queue depth and worker capacity in monitoring docs
- •If output quality is noisy, review smart grouping guidance and scope definitions
- •If ownership is unclear, enforce role path and escalation policy before scale-out
Escalation
Need onboarding help for enterprise rollout?
If your team is migrating multiple projects, use assisted onboarding to lock governance and operational defaults.