Projects and live audits
Set scope, run live audits, understand crawler behavior and interpret skipped or blocked pages.
Customers setting scope and technical reviewers
Feature availability
Product, package, provider and deployment boundaries for this page.
- Available from
- Current documentation
- Deployment modes
- cloud
Product screenshots
Current customer-safe screenshots are generated from the application so examples do not drift from the product.
Project setup path
Use this section when a customer is creating a project, proving authorization, accepting discovered scope, running a live audit or interpreting skipped pages. 
- Supported scopes
- Unsupported targets
- Public-page-only limits
- Accepted scan scope
- Manual URLs and include/exclude paths
- Ownership proof
- Set scan scope and run live audits
- Crawler behavior
- Browser rendering
- Data collected and excluded
- Screenshots and HTML snapshots
- Console and network evidence
- Privacy redaction
- Failure and skipped-page meanings
Live audit evidence path
Open [Projects](/projects), choose the owned project, review accepted scope, then start the scan only when plan, authorization and scope states are ready.
- Crawler behavior
- Browser rendering
- Data collected and excluded
- Screenshots and HTML snapshots
- Console and network evidence
- Privacy redaction
- Failure and skipped-page meanings
What to open next
- Use [Accepted scan scope](/docs/projects/accepted-scan-scope) before starting a private scan.
- Use [Set scan scope and run live audits](/docs/projects/scan-scope-and-live-audits) when the customer asks what to click next.
- Use [Failure and skipped-page meanings](/docs/projects/failure-and-skipped-page-meanings) when a page is skipped or blocked.
Was this page helpful?
Feedback goes into the product documentation review queue.