Areas
The hierarchy that gives every asset, process, and product an owner — and lets you read risk by area.
What they are for
Areas are your company's organizational structure inside the platform. They exist for a practical reason: risk with no owner does not get treated. Giving every asset, business process, and product a responsible area means "who looks after this" stops depending on who remembers.
Hierarchy
An area can have a parent area, so the structure follows the real org chart — division, department, team. The platform prevents cycles: an area cannot be its own ancestor, directly or indirectly, which rules out a hierarchy that never closes.
Risk by area
Every link between a supplier and a context object contributes risk to the area that owns that object. The magnitude comes from the supplier's latest assessment.
The per-area view shows two numbers, not one: the worst case and an average weighted by the criticality of the objects involved. Together they answer different questions — the worst case says whether something severe lives there, the weighted average says whether the area has a systemic problem. An area with one terrible supplier and nine excellent ones looks calm on average and is not. It also shows how many distinct suppliers touch the area, including those not yet scored.