Create your first project

Before you start

A first project tells WebRiskOps which owned website, storefront or SaaS property the account wants to scan. Create it after the owner account exists and before scope acceptance, domain ownership verification, service choice, billing checkout or the first live audit. Use this page when you can access the customer workspace and know the public production URL or approved test host. Keep the first project focused on one owned site so setup, billing, authorization, scope, project services and reports stay attached to the same target.

Create the project

Follow the path `Dashboard → Shortcut paths → Get the first useful report → Projects → Add project → New project modal → Project detail`. The completed project should show the domain, owning account, intake state, project services, scope status, domain authorization state and account entitlement readiness. If Shortest path to first useful report shows a blocked step, finish that exact automated next action before starting a scan.

1. Open `/dashboard` and choose Get the first useful report, or open `/projects` directly. Result: the Projects page shows Project next actions and the Add project button.
2. Click Add project. Result: the New project modal opens without adding a permanent form to the Projects page.
3. Choose the Account that should own billing, authorization, account entitlements and reports for this site. Result: the project will be attached to the correct workspace before any service is connected or scan runs.
4. Enter a clear Name and the public Domain or URL, for example https://www.example.com. Result: WebRiskOps can validate the host and show whether the target is public and supported.
5. Leave Optional setup details closed unless you already know Platform, Business type, Customer flow, Fix delivery path, Primary market or Notes. Result: the first project can be created without a long setup form, and missing choices stay visible for the next project action.
6. Click Create project. Result: WebRiskOps opens the project detail screen and shows Shortest path to first useful report with the current blocker and next action.
7. If Finish project setup appears, choose a preset or fill Business type, Customer flow, Fix delivery path and Platform, then click Save setup. Result: setup unlocks the next scope, authorization, billing, project-service or scan action without a separate planning page.

Continue to domain authorization

After the project exists, continue with the Authorize your domain documentation link on this page. The domain ownership check is one of the protected steps that stays explicit before private scan delivery.

Blocked states

• Domain is invalid means the URL is malformed, private, unsupported or missing a public host. Enter a public `http://` or `https://` URL owned by the customer account.
• No account is available means the signed-in user is not in a workspace that can own projects. Create the owner account or ask an account owner to invite the user before retrying.
• Unsupported target means the project should stop before scan setup. Use a supported public web property, split unrelated domains into separate projects, or wait for a later integration path.
• Project setup comes first means WebRiskOps needs the setup choices shown under Finish project setup before scope, billing or scan actions can move forward.
• Project service not connected means the project exists, but the service still needs account coverage and explicit enablement on the project page.