Skip to content
Governance Platform

Project-Scoped Indicators

In v1.0.0, customer-created indicators are scoped to a project. A project indicator can only monitor controls in the same project.

Why Scope Matters

Section titled “Why Scope Matters”

Project scoping keeps automated evidence aligned with project membership, policy applications, control records, and audit history. It also prevents an event intended for one project from updating another project’s evidence.

Indicator Lifecycle

Section titled “Indicator Lifecycle”
  1. A user creates the indicator inside a project.
  2. A user applies the indicator to one or more controls in that project.
  3. An integration sends events that identify the same project and indicator.
  4. Governance Service evaluates active applications.
  5. Results appear in the indicator, monitored controls, and generated declarations when configured.

Active and Disabled Applications

Section titled “Active and Disabled Applications”

An indicator application connects an indicator to a control. Disable an application when monitoring should pause. Delete or archive related governance work only when the control owner no longer needs that monitoring history.

Common Mismatches

Section titled “Common Mismatches”
  • Event uses the wrong project identifier.
  • Event uses the wrong indicator identifier.
  • Indicator is not applied to the expected control.
  • Indicator application is disabled.
  • Event fields do not match the JSONPath criteria.