Projects
Managing Projects
Why projects exist in Hygiara and how to use them properly.
What this page is for
This page explains what a project record actually does in Hygiara and how to decide when to create one.
When to use it
Read this when:
- you are setting up a new client or internal Azure estate
- you are not sure whether to create another project or another review
- your review history is starting to feel disorganised
How projects work
A project is the parent object for:
- saved Azure connections
- review history
- reports
That means the project structure affects the quality of everything that sits under it. Set it up right early and you rarely need to revisit it.
How to decide when to create one
Create a separate project when you want clean separation of:
- Azure access
- review history
- reporting outputs
That usually means one project per client, business unit, or clearly separate internal estate.
What to expect
You can rename a project at any time. Changing the structure after lots of reviews exist is more awkward than getting it right to start with, but renaming alone does not affect anything functionally.
Common mistakes
- creating a new project just because you want another review under a different name
- using vague names that make no sense in a review list six months later
- treating projects as optional labels rather than meaningful containers for access and history