#094Guide4 min
Follow several projects over time
Organize a repeatable review of connected projects using search, report freshness, open findings, and optional monitoring.
Hackaiz team · updated 21/11/2026

01Use the platform list as your starting point
When you maintain a customer portal, an internal tool, and an API, the first difficulty is knowing which system each result belongs to. Monitored projects lists the platforms in your workspace. Each card includes the project name and repository reference, the latest report status when available, and how recently it was scanned. Repository projects also show visibility and language; other target kinds have their own type badge. Read the target reference before opening a result.
Use Search platforms to narrow the list by name, repository, or address. The displayed matching count helps confirm that a search is active. Clear search restores the full list. This is a practical way to work through a portfolio without mistaking a filtered view for every connected system. Opening a card leads to the latest report if one is available, otherwise to analysis setup; it does not automatically launch a new review of every project.
02Separate urgency from freshness
Cards show open findings and the severity badges represented among them. Customer-facing severity groups are Danger, To fix, and To watch. Start with an urgent issue on a sensitive system, but also look for old or incomplete analyses. A low count on a long-unchecked application is not necessarily more reassuring than a recent report that found a specific, well-documented problem. “No open findings” is a recorded state, not a statement that every possible weakness has been excluded.
For example, a public account portal may need attention before an internal demonstration even if both show an open issue. Record that business context in your own review notes. Hackaiz supplies technical observations; your team decides which systems handle sensitive information, which releases are imminent, and who can approve changes. Do not present this suggested review order as an automatic business-priority calculation supplied by the platform.
- 1Open Monitored projects and clear any previous search.
- 2Check the target reference, report status, and scan age for each system under review.
- 3Open the relevant report to understand its unresolved findings.
- 4Record the next action and responsible teammate in your normal team process.
03Enable follow-up only where appropriate
The project detail page includes Monitor this project for eligible connected systems after a successful or partial analysis. Monitoring is optional: the title Monitored projects does not mean that every listed platform is already under automatic follow-up. Review the project’s switch and any displayed last automatic check or stop reason. A pasted address alone does not establish ownership or activate ongoing monitoring.
Monitoring uses configured checks and can react to detected changes. Watch activity and analyses consume credits; insufficient balance or expired authorization can suspend follow-up. Do not promise a fresh full analysis at every visit to the project list. For a website or API, establish domain ownership first using the supported DNS TXT or HTTPS verification file method. A GitHub repository connection does not remove the separate proof requirement for an associated live domain.
04Maintain a review trail per system
Use each project’s Scan history to connect a release to its report. The detail page also provides a comparison with the previous scan, so you can investigate newly appearing or missing findings within that project rather than comparing unrelated totals across applications. A database-backed service and a static website do not have identical exposure or analysis coverage. Keep conclusions attached to the target and checks that produced them.
After a correction, revisit the affected project instead of assuming that work on a shared codebase cleared every deployment. Where Hackaiz proposes a GitHub fix, it is a draft pull request for human review and approval, never an automatically merged change. Check the deployed version and obtain new evidence for the affected system. Keep old project records while they are useful: deleting a project also removes its analyses and history, so deletion is not a harmless way to tidy your review list.
Frequently asked questions
Take the next step
Was this article helpful?