Mailed approvals#
In the Enterprise Edition the people whose turn it is to approve a remediation plan are mailed, reminded and escalated. In the Community Edition the plan shows whom it would ask ("would ask") and nothing is mailed. This page extends Approvals and Mail in the Community guide.
What decides it#
core.approvals.requests is by-edition by default, in the chart and in core. An empty, absent or misspelt value is read as
by-edition, not as send.
| Value | Meaning |
|---|---|
by-edition |
send when the licence allows remediation beyond preview, which is Enterprise; show-only otherwise |
send |
The people whose turn it is are mailed, reminded and escalated, in every edition, when a relay is set |
show-only |
Nothing is mailed, reminded or escalated. The plan shows each step as "would ask", and answers on the screen still count |
A mail relay is needed#
A new install has no mail relay. Without one nothing is mailed whatever the setting says, and invitations and links are
handed over on screen. Name a relay as Mail describes, and set FRONTEND_URL, the public address,
because without it no link can be made.
Order, time and escalation#
The order (core.approvals.order: chain or any), the time a step may wait (core.approvals.stepTimeout, 5d as
shipped), the reminders (core.mail.approvals.reminderInterval, every 3d, twice at most) and the escalation are described on
Approvals. They apply in every edition. Escalation notices go by e-mail only.
Not covered#
Slack is not a channel yet: approval is by the screen and by e-mail. A step is escalated once; there is no second level. In 0.9.0 remediation is a plan a person reviews and applies: the approvals decide the plan, and Hyvop does not change or delete resources.