Projects

Projects represent the websites you want to check with the platform. Each project combines name, URL and an optional description and is the top-level entity for sitemaps, scan profiles and all resulting scans.

Create a project

• Enter a display name that you'll recognise in lists and selectors.
• Enter the base URL of the website (scheme and domain, optionally a path, depending on how your site is set up).
• The favicon is usually detected automatically and shown next to the project name, provided the URL is reachable.

Edit a project

• You can change name and URL if branding or domain change (mind the impact on existing sitemaps and profiles).
• Description - free text for internal notes, e.g. team, owners or hints about the site structure.

Good naming

• Use unambiguous names when you maintain several similar sites (e.g. "Shop DE" and "Shop AT").
• Avoid purely technical codes without context if several people in the workspace will read them.

Archive

• Projects you don't need for the moment should be archived rather than deleted, unless deletion is explicitly intended.
• Archived projects are usually read-only: master data can no longer be changed and the UI makes that clear.
• Scan profiles for the project are paused and are no longer available for normal, scheduled runs as they would be for an active project.

Reactivate

• Bring a project back from the archive when the website should be checked again.
• After reactivation, check URL, sitemap and scan profiles to make sure everything still matches the current site.

Permanently delete

Projects can be permanently deleted by workspace administrators (roles OWNER and ADMIN). This action cannot be undone and is deliberately distinct from "archive".

Who is allowed to delete?

• Only members with the Owner or Admin role see the entry in the three-dot menu on the project detail page.
• Members and read-only users have no access to this function.

Preconditions

• No scan in status RUNNING, PENDING or RESERVED may be active. Otherwise the delete button in the menu is disabled. Cancel the scan first or wait until it has finished.

What is deleted?

• The project itself (name, URL, favicon, notes, colour)
• All sitemaps and their analysis data
• All scan profiles including assigned URLs and schedules
• All scans of the project including findings, scan results, preflight checks and quick checks
• Token reservations and project-specific guardrail policies
• Content assessment rules and project-specific rule overrides
• Project-specific ignore-list entries
• Project-specific notification configurations
• Project memberships (the user accounts themselves are kept)
• The file attachment of the project favicon in storage

What is kept?

• Token billing data (TokenUsage continued with projectId = null) - so your consumption and invoice history stays consistent.
• Audit-log entries for the project - the events project.delete.requested and project.delete.completed (or project.delete.failed) are kept in an audit-proof manner.
• Anonymised platform statistics: the project's KPIs (number of scans, checked URLs, found / fixed findings) are written as an anonymous entry to the platform KPI journal before deletion, so that public live statistics on the landing page stay consistent.

Process

1. From the three-dot menu on the project detail page choose "Permanently delete".
2. In the confirmation dialog read the notes and confirm with "Permanently delete". If you're unsure: cancel and use "Archive" instead.
3. The platform starts the deletion in the background. You're redirected back to the projects overview and see a hint toast.
4. Once the deletion completes, all workspace members receive an in-app notification (bell icon top right).
5. On failure you receive an error notification; a watchdog reports automatically if the process hangs for more than 15 minutes.

Relationship with sitemaps and scans

• Sitemaps and scan profiles are always tied to a concrete project; switching the project switches the context.
• Scans appear in the history with a reference to project and profile so you can attribute results later.

FAQ

Why is no favicon shown?

• The URL might not be reachable, or the server doesn't provide a standard favicon.
• Check the base URL and whether redirects or protection mechanisms block the request.

Can I duplicate a project?

• If the UI doesn't offer duplication, create a new project with the same URL and copy the settings manually from the documentation.

Notes

• A project should represent one website - mixing several independent domains makes evaluation and token attribution harder.
• Before archiving: briefly check whether running scans or scheduled jobs still need to be considered.