#024Guide3 min
Manage several assets in Hackaiz
Find the right website, repository or database and keep each project’s results in context.
Hackaiz team · updated 21/11/2026

01Start with a clear inventory
A single application can involve a public website, a GitHub repository and a database. These are different targets, not interchangeable views of the same evidence. A repository check examines available code; a website check concerns the authorized domain. Keep the target address or repository identifier alongside the project name when deciding which result to open.
For example, a shop’s production domain and its test domain should not be confused simply because both display the same brand. Before connecting anything, make a short list of the targets you own or are authorized to assess. Note which environment each target represents. This is preparation you do yourself, not a promise that Hackaiz automatically groups every component of an application.
02Use Monitored projects to move between targets
The Monitored projects screen lists connected projects. Its cards show the project name, repository or target reference, latest scan status when available, and open findings. The title does not mean that optional monitoring has been activated for every entry. Use the list first as a way to identify and open the correct target.
The Search platforms field accepts a name, repository or address. Matching ignores letter case and accents and checks the words you enter against the project’s identifying information. The visible count shows how many platforms match out of the total. If a target seems missing, clear the search before assuming it was removed.
- 1Open Monitored projects from the workspace navigation.
- 2Enter a distinctive domain fragment or repository name in Search platforms.
- 3Compare the name and repository or address on the matching card.
- 4Select the card to open its available report; a project without a report takes you toward analysis.
03Do not mix evidence from different projects
Open findings are summarized per project, with the customer labels Danger, To fix and To watch. A card with no open findings is not a guarantee that every part of your application is secure. Check the actual report, its analysis status and what was covered before giving a colleague a conclusion about a specific environment.
When you need the project detail rather than the latest report, use the workspace magnifying glass. In Search, choose the matching item in the Projects group. That opens the individual project page, where Scan history lists its analyses. The shortcut only offers a limited selection of projects, so retain useful project-detail addresses when working with a large inventory.
For a practical handover, record the target, analysis date and the finding you want someone to review. Avoid forwarding a production issue with only a test-project name in the message. A precise reference is more useful than adding together finding counts from unrelated databases, sites and repositories.
04Connect and analyze each target deliberately
Use Connect when adding another authorized target. Websites and APIs require proof of domain control before analysis: a DNS TXT record named _hackaiz, an HTTPS file at /.well-known/hackaiz-verification.txt, or an instruction to the project’s AI to create that file. A similar name in your inventory does not replace this proof.
Before starting a new analysis, inspect the selected checks for that target. Actions use credits; do not treat a multi-project inventory as an unlimited batch allowance. Unticked checks are neither run nor billed. Optional monitoring applies only to connected systems, and an existing project in the list is not evidence that recurring checks are enabled.
The list also contains a Delete control. Do not use deletion merely to reduce visual clutter when search would do the job. First identify the exact project and read the confirmation presented by the application. Managing several assets safely is mainly about keeping authorization, target identity and report context aligned.
Frequently asked questions
Take the next step
Was this article helpful?