Customers
Managing Customers
Why customers exist in Hygiara and how to use them properly.
What this page is for
This page explains what a customer record is actually doing in Hygiara and how to decide when to create one.
When to use it
Read this when:
- you are deciding how to model a new client or internal estate
- you are not sure whether to create another customer or another review
- your review history is starting to feel messy
How customers work
A customer is the parent object for:
- saved Azure connections
- review history
- reports
That means customer structure affects the quality of everything that comes later.
How to decide when to create one
Create a separate customer when you want clean separation of:
- Azure access
- review history
- reporting outputs
That usually means one customer per client, business unit, or clearly separate internal estate.
What to expect
You can rename customers later, but changing the customer structure after lots of reviews exist is more awkward than getting it right early.
Common mistakes
- creating a new customer just because you want another review
- using vague names that make no sense in a review list six months later
- treating customers as optional labels instead of real containers