Notifications and propagation
Propagation in OneEnv is a decision, not a push.
By the OneEnv team · Last updated
What it is
The Notifications page is the inbox for decisions. There are six kinds: branch review, and five that concern consumers (environment propagation, database propagation, API propagation, validation propagation, and service override).
What happens at merge
- OneEnv records the old and new value of what changed.
- It creates one notification per changed item, with an impact score from 0 to 100 and a risk level (low, medium, high, critical).
- It creates one pending impact per service that currently inherits the item.
- The service that originated the change is approved automatically.
- If an earlier change to the same item is still unactioned for a service, that older impact is superseded so the service decides only on the latest value.
Impact score
The score blends reach (how many services), whether the change is breaking, whether a secret or structural delete is involved, and what share of affected services have nobody able to act on the change. The weights are a product choice, not a standard, and the score is computed once at merge. Treat it as a prioritisation hint, not a measurement.
Why export waits
A service's export resolves each key from its override, otherwise from the last value it approved. A merged change that a service has not approved does not appear in that service's export. This is what makes rejection meaningful.
Email and webhooks
Members can opt in to email and webhook delivery of notifications in their delivery settings. This is best-effort and secondary: the in-app Notifications page is the source of truth.
Common issues
- A member sees only notifications for services they can view. Owners and Admins see all.
- A change you expected to see missing for a service means that service did not inherit the item at merge time.