Projects
Project Workspace
How to use the project page to manage reviews, templates, schedules, and connection usage.
What this page is for
This page explains how to use the project page once a project already exists. It is the operational home for everything related to one client or Azure estate.
When to use it
Use the project page when:
- you are working on one project specifically
- you need to see which connections have been used by that project
- you want to launch a review without selecting the project again from a generic page
- you want to manage templates or schedules tied to this project

How to use it
KPI cards
At the top of the page you will see three summary cards:
- Latest review — the most recent review status. Click it to go straight to the review.
- Reviews — completed reviews out of total reviews for this project.
- Connections — how many reusable Azure connections have been used by this project.

Reviews tab
Use this tab to:
- see all reviews for this project
- check whether a review completed
- download a report
- start the next review from the project context
Access tab
Use this tab to:
- see reusable Azure connections that have been used by this project
- confirm which tenant or credential source previous reviews used
- avoid confusing unused organization-level connections with project history

Templates tab
Use this tab when you want repeatability rather than another one-off run.
A template saves a reusable review recipe for this project. Once the scope and connection are stable, saving a template means the next review takes seconds to queue.

Schedules tab
Use this tab to attach a cadence to a saved template.
Schedules are for projects that should be reviewed regularly without someone having to recreate the same run from scratch every week or month.

Starting a review from here
If you already know the review belongs to this project, this is the right place to launch it. The project is pre-selected and saved organization connections are available in the review flow.
What to expect
The project page becomes more useful as a project matures. A brand-new project mostly needs its first review. Once reviews are running, the Reviews tab becomes the main area. Once the scope is stable, templates and schedules are worth setting up.
Common mistakes
- launching from a generic page when you already know which project the review belongs to
- forgetting to validate a saved connection before an important rerun
- leaving repeatable projects on ad hoc review creation instead of saving a template