`essential_contacts_organization` — version 1.4

Source: presets/essential-contacts-organization.satz

Purpose

One organization-level Essential Contact, subscribed to every notification category Google routes.

One address may appear ONCE per parent — so the shipped shape is a single contact on ALL. To split by audience (billing to finance, suspension and security to the on-call, …), uncomment the per-category contacts below, give each its own address, and either narrow or delete the all contact: an address subscribed to ALL already receives every category.

Categories (API enum names): BILLING, LEGAL, PRODUCT_UPDATES, SECURITY, SUSPENSION, TECHNICAL — and ALL.

Use it

params {
  // the pack's own defaults — copy only the lines you change
  essential_contacts_email = "essential-contacts-all@{customer_domain}"
}

google_essential_contacts_contact { use "presets/essential-contacts-organization.satz" }

Needs from outside the pack:

customer_domain — declared by estate_core; use one of them alongside, or declare it in the estate.
customer_organization_id — declared by estate_core; use one of them alongside, or declare it in the estate.

Params

param	default
`essential_contacts_email`	`"essential-contacts-all@{customer_domain}"`

Questions

What to ask before this pack is configured, and what changing the answer costs.

asks about	prompt	reversal	blast	recommends
`essential_contacts_email`	The address that receives every Google notification for the organisation (a group, never a person)	edit	high	—

essential_contacts_email — Suspension notices, security advisories and legal notices go here and nowhere else. The mailbox must exist and accept external mail; a wrong address means Google's warnings are read by nobody until the consequence arrives.

Contributes

A bare list — keyed by the estate's resource map (google_x { use "presets/essential-contacts-organization.satz" } or use … as google_x): all.

Claims

None — this pack proves no control by itself.

History

version	date	change
1.4	2026-09-20	the header loses the word `content`, which the language no longer has: a pack header is a name and a version. Nothing emitted changes. A copy of 1.3 is refused by its header line — see Breaking changes
1.3	2026-09-10	one `question` block on the contact address: Google's suspension, security and legal notices go there and nowhere else. Nothing emitted changes
1.2	2026-09-02	commented per-category contacts (BILLING, SUSPENSION, SECURITY, TECHNICAL, LEGAL, PRODUCT_UPDATES, and a multi-category example) with their own address params, ready to uncomment; the shipped shape is unchanged (one contact on ALL)
1.1	2026-08-23	`essential_contacts_email` param — a customer pins its contact without a fork; content pack
1.0	2026-08-20	organization-wide essential contact, all categories

The whole library's history: the changelog in presets/CHANGELOG.md.

Notes

One address may appear only ONCE per parent, which is why the shipped shape is a single contact on ALL categories. Splitting by audience needs a distinct address per category — the six per-category contacts are shipped commented out for exactly that.

The CIS pack's contact-domain policy must allow the address's domain, or the apply is refused by the policy this estate itself set.

essential_contacts_organization — version 1.4